Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Apple App Store charts

apple_app_store_charts_list
Read-onlyIdempotent

Retrieve Apple App Store chart rankings with full app records, filtered by country, chart type, platform, genre, and result limit. Use it to analyze top free, paid, grossing, or new apps.

Instructions

List Apple App Store charts with full app records. Optional inputs: country, chart, platform, genre and limit. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "apple_app_store_charts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
chartNo`top-free`, `top-paid`, `top-grossing`, `new`, `new-free` or `new-paid`. `top-grossing` is available on iPhone and iPad; the `new` charts on iPhone only. Default: `top-free`.
genreNoGenre id to rank within, e.g. `6014` for Games or `6005` for Social Networking. Default: `36`, all apps.
limitNoRanks to return, 1-200 (1-100 for top-grossing and the new charts). Default: 100.
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`.
platformNo`iphone`, `ipad` or `mac`. Default: `iphone`.
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.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that records are 'full app records' (indicating a heavier payload) and 'Returns a list', but says nothing about pagination, result shape, or how the required context/llm_model/conversation_id parameters affect behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences and front-loaded with the verb and resource, which is good. However, the parameter enumeration duplicates the schema without adding value and 'Returns a list' is close to filler for a tool whose name already says 'list'.

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?

Adequate but thin for an 8-parameter tool with no output schema: the return value is only described as 'a list', giving no sense of the record shape despite the 'full app records' claim. It also omits that required bookkeeping parameters exist and how conversation_id sequencing constrains parallel calls.

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?

The description only enumerates parameter names ('country', 'chart', 'platform', 'genre', 'limit') without adding format, defaults, or meaning beyond them. Schema coverage is 100% and the schema already carries defaults and constraints, so 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 Apple App Store charts with full app records', which is concrete and distinguishable from review/detail/search siblings. It stops short of naming how it differs from ranking-style siblings like steam_charts_list, but the resource 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 Guidelines2/5

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

No when-to-use guidance, no exclusions, and no pointer to an alternative such as apple_app_store_apps_search for keyword lookups. The only implicit signal is that it lists charts, leaving the agent to infer the use case from the name alone.

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