SiteCheck Agent Intel & Dev

App Store iPhone app metadata from Apple's public iTunes

dev_apple_app_store_iphone

Read-only

App Store iPhone app metadata from Apple's public iTunes Lookup API by App Store id: name, seller, version, price, average rating and rating count, genre and release info. iPhone and universal apps. Ratings are Apple's counts for the chosen country. Related tools on this server, for a different need: dev_apple_app_store_reviews when you need App Store customer reviews of one iOS app from Apple's; dev_mac_app_store when you need Mac App Store app metadata from Apple's public iTunes. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "id": "<id>"
    },
    "name": "dev_apple_app_store_iphone"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	App Store track id, digits only, e.g. 425073498 (Procreate)
`country`	No	Two-letter store country code (default us)

Output Schema

Name	Required	Description	Default
`id`	No
`name`	No
`genre`	No
`price`	No
`seller`	No
`source`	No
`country`	No
`version`	No
`currency`	No
`storeUrl`	No
`checkedAt`	No
`ratingCount`	No
`releaseDate`	No
`averageRating`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the price model ($0.002 USDC per successful call via x402 on Base, Solana or Arc) and that failed calls are not charged – critical information for an agent deciding whether to call. It also clarifies that rating values are Apple's counts for the chosen country, preventing misreading of the returned data.

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?

Three dense sentences with the resource description front-loaded, followed by alternatives and then cost. Minor density from semicolon-chained pricing clauses, but no sentence is redundant given that billing terms must be stated.

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

Completeness5/5

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

For a two-parameter read tool with an output schema, the description supplies everything an agent needs: what it returns, which country scope applies, what siblings to use instead, and the per-call cost. Return values are correctly left to the output schema.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by framing lookups as 'by App Store id' and by explaining that rating counts are scoped to the selected country, which gives the country parameter significance beyond its schema text.

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 verb and resource (App Store iPhone app metadata from Apple's public iTunes Lookup API) and enumerates the returned fields: name, seller, version, price, ratings, genre, release info. It also scopes the resource to iPhone/universal apps, which distinguishes it from the Mac App Store sibling.

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?

Explicitly routes the agent: use dev_apple_app_store_reviews for customer reviews of one iOS app and dev_mac_app_store for Mac App Store metadata. Both alternatives are named together with the need that selects them, leaving nothing to guess.

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

All SiteCheck Agent Intel & Dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?