Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Install stats

store_installs
Read-onlyIdempotent

Retrieve an app's install statistics for a date range, including daily, weekly, and monthly buckets, per-version shares, and top devices.

Instructions

Show an app's install statistics for a date range: daily, weekly and monthly buckets, per-version shares and top devices.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "store_installs"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesstore UUID, manifest id, or exact app title
endNoend date YYYY-MM-DD; default today
startNostart date YYYY-MM-DD; default 30 days before end

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description earns credit by disclosing the return shape (bucketed time series, per-version shares, top devices), which matters because no output schema exists. It omits any note on aggregation limits, maximum range, or truncation of 'top devices'.

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?

A single front-loaded sentence with a colon-delimited list of report contents; every clause conveys distinct information and nothing is wasted.

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?

For a three-parameter, read-only analytics tool with no output schema, the description supplies the return-content outline that the structured fields cannot. Auth requirements and any range limits are still undocumented, which keeps it short of a 5.

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%; the schema already explains that 'app' accepts a store UUID, manifest id, or exact title, and documents the YYYY-MM-DD defaults for start/end. The description only restates the date-range concept without adding format or edge-case semantics, 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?

States a specific verb and resource ('Show an app's install statistics') and enumerates the report's contents (daily/weekly/monthly buckets, per-version shares, top devices), which clearly separates it from ratings/reviews siblings. It stops short of naming any sibling explicitly, so differentiation is inferred from the resource noun rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the phrase 'for a date range' plus the schema's defaults, so an agent can tell this is the tool for install-metric reporting. There is no explicit when-not, no prerequisite/permission note, and no pointer to the other store_* analytics tools, leaving selection guidance at the minimum-viable level.

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