Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple App Store app details

apple_app_store_app_details_get
Read-onlyIdempotent

Fetch Apple App Store app details, including rating histogram and version history, by numeric app ID and storefront country.

Instructions

Get Apple App Store app details like rating histogram and version history. Requires appId.

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_details_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the hint that results include rating histogram and version history; it says nothing about storefront-dependent variation or response size, so it adds modest value beyond the structured fields.

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?

Two short sentences, front-loaded with purpose before the requirement. The second sentence largely duplicates the schema's required list, which is minor waste but not harmful.

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 single-app lookup with no output schema, the description plus the fully documented schema and annotations cover what an agent needs to invoke it correctly. The only gap is the absence of any note on what the returned detail set contains beyond two example fields.

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%, with appId, country, context, llm_model and conversation_id all documented in the schema itself. The description's mention of appId adds nothing new, so the baseline of 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?

The description gives a specific verb and resource (get Apple App Store app details) and names two concrete payload elements, rating histogram and version history, which tells an agent this is a deep detail call rather than a search or batch call. It does not explicitly differentiate from the close sibling apple_app_store_app_get, so it stops short of a 5.

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

Usage Guidelines2/5

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

The only usage statement is 'Requires `appId`', which restates the schema's required field. There is no guidance on when to choose this over apple_app_store_app_get, apple_app_store_apps_batch_get, or the reviews/histogram-specific siblings, and no stated exclusions or prerequisites.

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