Skip to main content
Glama
shopify-partners-mcp

shopify-partners-mcp

by amitray007

install_summary

Read-only

Counts installs, uninstalls, deactivations, and reactivations per app within a specified time range to analyze app adoption and churn.

Instructions

Count installs, uninstalls, deactivations, and reactivations per app for a time range.

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": "install_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdNoApp ID: the number or a gid:// ID
occurredAtMaxNoEnd of the window. Defaults to now; the window is at most 365 days
occurredAtMinNoStart of the window. Defaults to 30 days before the end

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are counts grouped per app over a range, but says nothing about the window cap (365 days), the default range, or whether results are totalled or bucketed over time — details that would help an agent predict output.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the metrics and grouping come before the time-range qualifier. It is efficient, though very sparse for an aggregation tool.

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?

With only three optional parameters, full schema coverage, and read-only annotations, the definition gives enough to call the tool correctly. The main gap is the return shape — since there is no output schema, it is unclear whether counts are per-day buckets or a single total per app.

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

Parameters3/5

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

Schema description coverage is 100%, with appId, occurredAtMin, and occurredAtMax each documented including defaults and the 365-day cap. The description only echoes "per app" and "time range", adding no meaning beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb ("Count") plus the exact metrics (installs, uninstalls, deactivations, reactivations) and the grouping ("per app") over a time range, which is concrete enough to distinguish it from metric tools like revenue_summary or churn_report. It stops short of explicitly naming a sibling it replaces or contrasting scenarios.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned. An agent must infer from the metric names that this is the lifecycle-event count tool rather than a revenue or retention tool.

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