Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

mrr_movement

Read-only

Track monthly recurring revenue and its new, reactivation, expansion, contraction, and churn movements by amount and shop count for a Shopify app.

Instructions

Monthly recurring revenue per month with its movement: new, reactivation, expansion, contraction, and churn, in amounts and shop counts. MRR counts flat-rate subscription prices (annual plans divided by 12) of installed, non-frozen shops past their trial. Usage charges are not MRR; see earnings_by_month. Computed from the app's full event history, which the server downloads once and caches for 15 minutes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mrr_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNoApp ID: the number or a gid:// ID. Optional when SHOPIFY_PARTNER_APP_IDS names exactly one app
monthsNoHow many calendar months, ending with the current one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine semantics beyond that — the MRR inclusion rule (flat-rate subscription prices, annual/12, installed non-frozen shops past trial) and the 15-minute server-side cache of full event history — but omits return shape specifics such as ordering or whether zero-movement months appear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the metric and its breakdown, followed by inclusion rules and then the exclusion/pointer to the sibling. No filler, no restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description at least characterizes the return as per-month amounts and shop counts across five movement types, which is enough to know what to expect. It stops short of naming the exact fields or ordering, so an agent must inspect the result to build a UI.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, baseline is 3. The description adds one real clarification: that the series implicitly ends with the current month and is derived from the app's full event history, not just the requested window, which affects interpretation of the months parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific metric (monthly recurring revenue) plus its movement components — new, reactivation, expansion, contraction, churn — and states the units (amounts and shop counts). It also explicitly separates itself from earnings_by_month by declaring usage charges are not MRR.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to earnings_by_month for usage charges, which is a real alternative in the sibling set. It does not address when to prefer churn_report, revenue_summary, or retention_cohorts, but the key ambiguity for this metric family is resolved.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.