Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Apple App Store developer

apple_app_store_developer_get
Read-onlyIdempotent

Retrieve an App Store developer profile and every app they publish by supplying a developer ID, so you can analyze a publisher's app portfolio.

Instructions

Get an App Store developer and every app they publish. Requires developerId.

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

Input Schema

NameRequiredDescriptionDefault
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.
developerIdYesRequired. App Store developer id, e.g. `284882218` for Meta Platforms. It is the `developer.id` on every app.
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 fully covered. The description adds the meaningful scope detail that the response bundles every published app, but says nothing about result volume, pagination, or whether a missing developer id errors versus returns empty.

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 resource and its payload scope. The closing 'Requires developerId' is largely redundant with the schema's required field and its 'Required.' description, which keeps it from a 5.

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?

The description does state the return shape (developer record plus all their apps), which matters since there is no output schema. However, for a six-parameter open-world tool it omits any hint about storefront/language sensitivity of the returned data or how a large app list is delivered.

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 coverage is 100%, so all six parameters, including country, language, and conversation_id, are documented in the schema itself. The description's only parameter note ('Requires developerId') merely restates the required array, adding no new meaning.

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?

Specific verb+resource ('Get an App Store developer') plus a scope note ('and every app they publish') tells the agent exactly what comes back. It does not name or distinguish itself from near neighbors such as apple_app_store_app_get or stan_store_creator_get, but the payload is unambiguous.

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?

Usage is only implied: the mention of one developer plus all their apps lets an agent infer this is the right choice when it has a developer id rather than an app id. There is no explicit when-to-use, when-not, or pointer to an alternative for app-level lookups.

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