Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Apple App Store reviews

apple_app_store_app_reviews_list
Read-onlyIdempotent

Fetch customer reviews for an Apple App Store app, including developer replies. Filter by country and sort by recent, helpful, favorable, or critical, with pagination via app ID.

Instructions

List customer reviews for an Apple App Store app with developer replies. Requires appId. Returns a list (use page when paginated).

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": {
      "appId": "<appId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "apple_app_store_app_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based), 20 reviews a page, up to page 5,000. A deep page of a very long list can come back empty with `depthLimited: true`; ask again or try another sort; stop at the first empty page. Default: 1.
sortNo`recent` (newest first), `helpful` (Apple's own ranking), `favorable` (newest 5 star reviews only) or `critical` (newest 1 star reviews only). Default: `recent`.
appIdYesRequired. Numeric App Store app id, e.g. `284882215`. An id with the `id` prefix used in App Store links (`id284882215`) is also accepted.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter storefront code, e.g. `us`, `gb` or `jp`, case-insensitive. Prices, ratings, reviews and text are specific to it. A code Apple does not run a store for is refused. Default: `us`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety behavior needs no restating. The description adds that results include developer replies and that a paged list is returned, but says nothing about ordering, page size, or the empty-page/depthLimited behavior that the schema documents.

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 short sentences, front-loaded with the purpose and the required parameter. No wasted clauses, though the trailing '(use page when paginated)' is slightly awkward and could be folded into the paging sentence.

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 read-only list tool with full schema coverage, four annotations and no output schema, the description covers purpose, required input and return shape adequately. The remaining gaps (sort semantics, empty-page handling) are already covered by the schema, so nothing an agent needs to call it correctly is missing.

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%, so every parameter (page, sort, appId, country, context, llm_model, conversation_id) is already documented in detail. The description only restates that appId is required and gestures at paging, adding no meaning beyond the schema; 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 ('List customer reviews for an Apple App Store app') and adds a distinguishing detail ('with developer replies'). It is clearly separable from Steam/Shopify/Yelp review siblings by platform, though it never names an alternative tool explicitly.

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?

The only usage guidance is the parenthetical '(use page when paginated)', which hints at paging but gives no rule for when to page versus re-sort or stop. There is no when-to-use/when-not-to-use framing relative to app details or other review tools; the richer paging and sort guidance lives in the schema, not the description.

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

Deploy Server

Other Tools