Skip to content
HeyCrustDocs

Search documentation

Search by topic or tool name
Partner portalOpen app ↗
Browse documentation
Tool reference

get_churn_analysis

Returns definition, monthlyChurn and uninstallReasons.

Verified ·Read Markdown
On this page

Purpose

Monthly subscription churn rates (complete months only) plus the uninstall-reason breakdown. Call when asked why merchants leave, what churn looks like, or which reasons dominate.

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
  • reasonDays: optional; integer; minimum: 1; maximum: 3650; default: 90 — Window for the uninstall-reason breakdown, in days. Default 90.

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.

json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_churn_analysis",
    "arguments": {
      "appId": "11111111-1111-4111-8111-111111111111",
      "reasonDays": 90
    }
  }
}

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 definition, monthlyChurn and uninstallReasons. Opening paid shops losing their last app subscription are counted once per month; billing freezes are excluded from that cancellation/uninstall churn definition.

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.

Continue reading