Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get many Apple App Store apps

apple_app_store_apps_batch_get
Read-onlyIdempotent

Fetch details for up to 200 Apple App Store apps in one request by submitting App Store links, numeric app IDs, or bundle IDs, with optional storefront and language settings.

Instructions

Get up to 200 Apple App Store apps in one request. Requires url. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. An App Store link, numeric app id or bundle id. Repeat `url` for each app, up to 200. A repeated id or bundle id is billed once; an id and its bundle id are separate references. Every app is looked up in `country`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoTwo-letter App Store storefront (country) code, e.g. `us`, `gb`, `jp`. Every app in the request is looked up in this storefront, whatever storefront a pasted link names. 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.4/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 the safety profile is covered. The description adds only the 200-item ceiling and 'Returns a list' — useful because no output schema exists, but it omits partial-failure behavior, per-id lookup cost (documented only in the schema), and truncation semantics.

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 operation and its batch limit, with no filler. Minor redundancy in restating 'Requires url', which the schema already enforces as required.

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

Completeness3/5

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

For a six-parameter batch tool with no output schema, the description should say more about the shape of results per app and what happens when some ids fail. It covers the essentials (limit, required input, list return) but leaves the agent guessing about multi-item error handling.

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 explains url, country, language, context and llm_model in detail. The description only restates that url is required, adding no new meaning beyond the structured fields; 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 ('Get ... Apple App Store apps') and adds real scope information: 'up to 200 ... in one request.' The batch nature implicitly distinguishes it from the singular apple_app_store_app_get, but it never names or contrasts an alternative, so it falls 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 Guidelines3/5

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

The phrase 'in one request' hints that this is the efficient choice when many apps are needed, but there is no explicit when-to-use, when-not-to-use, or named alternative such as apple_app_store_apps_search. The agent must infer the batching rationale.

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