Skip to main content
Glama

Search App Store apps or look one up by its id

apps_search
Read-only

Searches the App Store (iTunes Search API) by keyword, or looks up one app by its numeric id: name, developer, bundle id, price, rating and rating count, genres, version, release and update dates, size and store link. Country sets the storefront (default us). Ratings are the store's averages for that country. Limit max 50. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apps_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeywords for search (1-100 characters), or omit when using id
idNoNumeric App Store id, e.g. 570060128 (instead of q)
limitNoResults, 1-50 (default 10)
countryNoTwo-letter storefront code, default us

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
countryNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the cost model ($0.002 per successful call), the payment rail (x402, USDC on Base, Solana and 10 more networks), and that failed calls are not charged — critical information an agent cannot get from annotations. It also clarifies that ratings are country-specific store averages, not global, which changes how results should be interpreted.

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?

Purpose is front-loaded in the opening clause, followed by compact clauses on return fields, defaults, and pricing — no filler sentences. The first sentence is long and list-heavy, but each item carries information, so little is wasted.

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

Completeness5/5

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

For a read-only, open-world search tool with an output schema, everything an agent needs is present: mode selection, defaults, result cap, geographic scoping of ratings, and the billing consequence of calling it. The field enumeration is arguably redundant with the output schema, but it does no harm at this length.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description earns above that by adding meaning the schema lacks: country determines the storefront and therefore which average ratings are returned, and limit's hard ceiling of 50 is restated as a constraint. It still does not explain id-vs-q precedence if both are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Searches the App Store (iTunes Search API) by keyword, or looks up one app by its numeric id" gives a specific verb, resource, and both operating modes, then enumerates the returned fields (name, developer, bundle id, price, rating, genres, version, dates, size, link). An agent can immediately tell this apart from github_search, hn_search, or package_search by resource domain alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It states the selection condition between the two modes clearly: use q for keywords, or omit q when using the numeric id. It also gives defaults (country=us, limit default 10, cap 50). What is missing is any explicit exclusion or when-not-to-use guidance, though the domain makes alternatives self-evident.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources