SiteCheck Agent Intel & Dev

App Store customer reviews of one iOS app from Apple's

dev_apple_app_store_reviews

Read-only

App Store customer reviews of one iOS app from Apple's public reviews feed: for each review the star rating, title, text, author name, app version, date and helpful-vote counts, 50 per page, newest or most helpful first, with the page's average rating. Give the numeric App Store id (or an apps.apple.com link) and a store country. Apple serves 10 pages (500 reviews) at most; an app with no reviews in that country is a 404 and not charged. Related tools on this server, for a different need: dev_apple_app_store_iphone when you need App Store iPhone app metadata from Apple's public iTunes; 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_reviews"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	App Store id, digits only, e.g. 284882215 (Facebook), or an apps.apple.com link that contains it
`page`	No	Page 1 to 10, 50 reviews each (default 1)
`sort`	No	recent (default) or helpful
`country`	No	Two-letter store country code (default us)

Output Schema

Name	Required	Description	Default
`page`	No
`sort`	No
`appId`	No
`count`	No
`source`	No
`country`	No
`reviews`	No
`lastPage`	No
`checkedAt`	No
`averageRatingOnPage`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

changedInput schema / properties / id / description

Previous value: -"App Store id, digits only, e.g. 310633997 (WhatsApp), or an apps.apple.com link that contains it"New value: +"App Store id, digits only, e.g. 284882215 (Facebook), or an apps.apple.com link that contains it"

AddedNov 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial behavior on top: 50 reviews per page, newest or most-helpful ordering, the page's average rating, a hard 10-page cap, a 404 for regions with no reviews, and no charge for failures. Pricing and payment rails (x402 on Base, Solana or Arc at $0.002 per successful call) are disclosed up front, which matters for a paid endpoint.

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?

It is front-loaded with the resource and its payload before moving to inputs, limits, alternatives and price, and every sentence carries information. The single dense paragraph and the appended pricing/alternatives block make it slightly heavy to scan, but there is no filler.

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?

With an output schema and full parameter coverage already present, the description only needs to supply limits, failure semantics and cost, all of which are stated. Nothing an agent requires to decide, call or interpret this tool is missing.

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 constraints the schema does not spell out: the 10-page/500-review ceiling that bounds 'page', and the fact that a country with no reviews returns 404 rather than an empty list. The id-format note largely repeats the schema's own description, so it is not a full 5.

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?

The description names a precise resource (customer reviews of one iOS app from Apple's public reviews feed) and enumerates the returned fields, page size and sort orders. It explicitly separates itself from dev_apple_app_store_iphone and dev_mac_app_store, which cover metadata for different platforms, so an agent can pick the right tool without opening schemas.

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?

It states the required inputs (numeric App Store id or apps.apple.com link, plus a store country) and routes other needs to the named sibling tools. The 10-page/500-review ceiling and the 404-on-no-reviews case tell the agent what outcomes to expect, which is the practical when-not guidance for this tool.

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?