Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple App Store app

apple_app_store_app_get
Read-onlyIdempotent

Retrieve an Apple App Store app's price, ratings, version, genres, and screenshots by app ID or bundle ID for storefront-specific app research.

Instructions

Get an Apple App Store app: price, ratings, version, genres, screenshots and more, by app id or bundle id. 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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesRequired. App Store app id (digits, e.g. `284882215`) or bundle id (e.g. `com.facebook.Facebook`). 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`.
languageNoLanguage of the text, as `ll-cc`, e.g. `es-mx` or `ja-jp`. Changes the language of descriptions and price labels inside the storefront. Default: the storefront's own language.
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 covered by structured data. The description adds the shape of the returned payload, but says nothing about how country/language alter results or about the conversation_id sequencing constraint the schema raises.

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 the verb and resource, with the identifier hint in the second position. "Requires `appId`" is partly redundant with the schema's required list, which is the only wasted clause.

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-record fetch with no output schema, it names the main fields a caller gets back, which is the key missing piece. The only real gap is the unresolved overlap with apple_app_store_app_details_get, which the description never addresses.

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 the schema already documents appId, country, language, context, llm_model and conversation_id in detail. The description's mention of app id vs bundle id merely restates what the appId schema field already explains, adding no new semantics.

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 ("Get an Apple App Store app") and enumerates returned fields — price, ratings, version, genres, screenshots — plus accepted identifier forms. It does not distinguish itself from the nearby sibling apple_app_store_app_details_get, leaving the agent to guess which one to pick.

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 description only states a prerequisite ("Requires `appId`") and the accepted id forms. It gives no when-to-use context, no exclusions, and no routing to the obvious alternatives (app_details_get, apps_batch_get, apps_search), which matters because a sibling with a nearly identical name exists.

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