App Store Opportunity Tracker

Abandoned apps in search (off)

app_tracker_abandoned

Read-onlyIdempotent

Off: always answers source_off. The scan behind it reads App Store search results, search suggestions, reviews and HTML chart pages, which robots.txt or Apple's terms do not allow, so it does not run. Say that this scan is off, and offer app_tracker_opportunities, whose stale flag marks chart apps with no update for over 180 days.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

Name	Required	Description
`genre`	No	Apple genre id such as 6007 (Productivity) or a genre name. Default 6007.
`limit`	No	How many apps to return, 1 to 100. Default 25.
`country`	No	Two-letter store country, such as us, gb or jp. Default us.
`min_days`	No	Only apps with no update for at least this many days. Default 365.
`min_ratings`	No	Only apps with at least this many ratings. Default 100.

Output Schema

Name	Required	Description
`apps`	Yes
`note`	Yes
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`count`	Yes
`genre`	Yes
`store`	Yes
`source`	Yes	Who the data comes from, to cite and to check it against.
`country`	Yes
`filters`	Yes
`coverage`	Yes
`unproven`	No
`updatedAt`	No
`untrusted_source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only and idempotent profile, but the description goes well beyond them: it discloses that the tool always returns a fixed value, that no network scan occurs, and the legal reason (robots.txt and Apple's terms). That's exactly the kind of context an agent needs to avoid retrying or misreporting results.

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 operative fact ("Off: always answers source_off"), then the reason, then the redirect. No filler; each sentence does distinct work.

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 an output schema present and annotations covering safety, the description supplies the behavior, the rationale, and the fallback path. The only omission is that the five documented parameters have no effect on the fixed response.

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 coverage is 100%, so all five parameters are fully documented in the schema; baseline is 3. The description adds nothing about the parameters and, notably, never says they are ignored because the tool always returns source_off, leaving a small ambiguity about whether supplying genre/limit changes anything.

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?

"Off: always answers source_off" states the exact behavior in the first clause, and the following sentence explains what the tool would have done and why it doesn't. An agent immediately knows this is a disabled scan, not a working app-discovery tool.

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

Usage Guidelines5/5

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

Gives an explicit instruction on what to tell the user ("Say that this scan is off") and names a concrete alternative, app_tracker_opportunities, including the specific feature to point at (the stale flag for chart apps idle 180+ days). This is textbook when-not/use-instead guidance.

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

All App Store Opportunity Tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.