get_customer

Purpose

Full lifecycle detail for ONE merchant: status, plan, lifetime revenue, contact, and the complete event timeline with churn reasons. Call after list_customers when the question is about a specific shop.

Credentials and scope

Owner workspace credential. The credential determines tool visibility. For tools with appId, use the HeyCrust app UUID from list_apps; the dashboard app selector does not supply MCP arguments for you.

Inputs

• appId: optional; string or null
• shopDomainOrInstallId: required; string; minLength: 1 — A myshopify.com domain or the install id (shop GID) from list_customers.

Example request

The identifiers and merchant are fictional. Replace them with records returned for your own workspace; this example is schema-checked, not a promise that the fictional record exists.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_customer",
    "arguments": {
      "appId": "11111111-1111-4111-8111-111111111111",
      "shopDomainOrInstallId": "example.myshopify.com"
    }
  }
}

POST this JSON to https://heycrust.com/api/mcp with Content-Type: application/json and Authorization: Bearer <YOUR_CREDENTIAL>. The tool result normally contains JSON encoded as text in result.content; inspect JSON-RPC errors and result.isError before using it.

Result

Returns the matched installation/customer detail or a lookup error. Exact domain lookup can be ambiguous across apps; provide appId and inspect the returned record.

Effects and verification

Reads existing records or definitions. It does not create a payment or send a message. Verify the returned app/merchant identity and source coverage before interpreting the result.

Troubleshooting

A missing tool can mean that the credential lacks its catalog or required scopes. Invalid arguments are different from unavailable source data or a record outside the workspace. A handler can return a business error even when the argument schema is valid. Read MCP overview and Help.