Skip to main content
Glama

App Store search

search_app_store
Read-only

Live App Store search for a keyword. Returns ranked apps and difficulty. With appStoreId, ranking is computed from all totalApps results, independently of limit; null means not found in those results. metadataIncomplete counts returned apps whose details are unavailable. Counts toward the research quota. Defaults to 10 apps (max 100). Compact app fields; no image URLs. Unavailable names are omitted.

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": {
      "term": "<term>"
    },
    "name": "search_app_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNo
storeNous
platformNoiphone
appStoreIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +10
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses quota consumption, default and maximum result counts, compact payloads with no image URLs, omission of unavailable names, and how ranking behaves when appStoreId is supplied. These are exactly the operational facts an agent cannot get from the annotations or schema.

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?

Five short sentences with the core capability front-loaded and no filler. Some sentences are telegraphic fragments ("Compact app fields; no image URLs.") that trade readability for density, and terms like "difficulty" and "totalApps" appear without context.

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

Completeness4/5

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

With no output schema, the description still explains the main return elements (ranked apps, difficulty, metadataIncomplete, null appStoreId) and the pagination ceiling. It leaves the meaning of "difficulty" and "totalApps" undefined, which is a modest gap for a search tool.

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 0%, so the description carries the burden; it explains limit (default 10, max 100) and adds real meaning to appStoreId (ranking computed from all totalApps results, null when absent). However, store and platform parameters are never mentioned, and term/limit simply repeat the schema constraints.

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?

Opens with a specific verb+resource ("Live App Store search for a keyword") and states the return shape ("ranked apps and difficulty"), which separates it from the tracked-app siblings like list_apps and get_app_details. It never names an alternative tool, so differentiation is inferred rather than stated.

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 implied by "Live search" versus the stored-app siblings, and "Counts toward the research quota" hints that this is a metered call worth rationing. There is no explicit when-to-use/when-not guidance or a named alternative for keyword-only lookups.

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