Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Apple App Store

apple_app_store_apps_search
Read-onlyIdempotent

Search the App Store by keyword across storefronts and platforms to find matching apps, returning up to 200 results for app discovery and comparison.

Instructions

Search the App Store for apps by keyword in any storefront, up to 200 results. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "apple_app_store_apps_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return, 1-200. Search often has 10 to 20 percent fewer results than asked for, so a shorter list is not an error. Default: 50.
queryYesRequired. Search text.
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.
platformNoWhere to search: `iphone` (iPhone and iPad apps), `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.2/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-result ceiling and "Returns a list", and omits the schema's important caveat that result counts often fall short of the requested limit.

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 core action and scope. Slight redundancy in repeating the required-query and 200-result facts that the schema already carries, but nothing is bloated.

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 an 8-parameter tool with no output schema, the description is thin: it says only "Returns a list" without indicating what fields a result carries. The unusual required parameters (context, llm_model, conversation_id) are explained only in the schema, not the description.

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 query, limit, country, language, platform and the analytics/conversation parameters. The description merely restates that query is required and the 200 cap, adding no meaning beyond the schema.

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 ("Search the App Store for apps by keyword") plus scope ("any storefront, up to 200 results"). It is clearly distinguishable from detail-oriented siblings like apple_app_store_app_get or apple_app_store_charts_list, though it never names them.

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 or when-not-to-use guidance. It does not say to prefer charts_list for top charts or app_get once an app ID is known, nor does it mention the batch_get follow-up path. Usage is only inferable from the verb.

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