Skip to main content
Glama

Search store

search_store
Read-onlyIdempotent

Search a store for apps by name or keyword (listing metadata for up to 12 results, flagged when already tracked).

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>",
      "store": "<store>",
      "country": "<country>"
    },
    "name": "search_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesSearch term.
storeYesStore. Google Play needs GOOGLE_PLAY_SOURCE on the deployment.
countryYesTwo-letter ISO 3166 storefront code, e.g. US, GB (not UK), IN.
languageNoBCP 47 language tag, e.g. en or pt-BR. Defaults to en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code, e.g. US, GB, IN."New value: +"Two-letter ISO 3166 storefront code, e.g. US, GB (not UK), IN."
    • addedInput schema / properties / country / maxLength
      Added value: +2
    • addedInput schema / properties / country / minLength
      Added value: +2
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / language / description
      Previous value: -"Language code, e.g. en. Defaults to en."New value: +"BCP 47 language tag, e.g. en or pt-BR. Defaults to en."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds real value by disclosing the 12-result cap and the already-tracked flag, but it never says whether the cap is a hard truncation or whether more results can be paged, which matters for an open-world search.

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?

A single well-formed sentence with the verb and resource front-loaded and secondary facts in a compact parenthetical. No filler, though the parenthetical packs two distinct behaviors into one clause.

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 correctly spends its words on the return shape (listing metadata, 12-result ceiling, tracked flag), which is the highest-value gap to fill. It stops short of describing the listing fields or failure modes, but for a simple search that is a minor omission.

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%, including the enum for store and the ISO-3166 pattern for country, so the schema carries parameter meaning. The description adds no syntax, defaulting, or interaction detail (e.g. how language affects matching) beyond what the schema already states.

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 (search) plus resource (store apps) and the matching mode (by name or keyword). It does not differentiate from siblings like top_charts, new_releases, or check_listing_metadata, so an agent must infer that this is the free-text entry point rather than a browse or lookup tool.

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 phrase 'by name or keyword' suggests when a search is appropriate, but no alternative tool is named and no exclusion is given. Nothing tells the agent to prefer top_charts or new_releases when it lacks a search term, or to follow up with check_listing_metadata.

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