Skip to main content
Glama

App Pain API

Search apps

search_apps
Read-onlyIdempotent

Search the iOS App Store and Google Play (both merged by default) to find apps and their ids; WordPress plugins / Chrome extensions / Steam games via store:"wordpress"|"chrome"|"steam". Use this FIRST when you only know an app name or a category.

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": {
      "q": "<q>"
    },
    "name": "search_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYessearch query, e.g. "habit tracker" or "notion"
limitNomax results per store, default 10
storeNolimit to one store (default: iOS + Android merged; the others need to be passed explicitly)
countryNoISO country code, default "us"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 genuine behavioral context by stating that iOS and Android results are merged by default and that other stores must be opted into. It says nothing about result ordering, relevance ranking, or what a merged multi-store result set looks like.

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

Conciseness5/5

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

Two sentences, zero filler, with the store scope established before the usage directive. Every clause carries information an agent needs.

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?

For a four-parameter read-only search with no output schema, the definition covers scope, defaults, and entry-point usage. It partially addresses return content ('find apps and their ids') but leaves result shape, ordering, and pagination unaddressed.

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 all four parameters including the store enum and country default are already documented. The description largely restates the merge default rather than adding new meaning such as ranking behavior or how the per-store limit interacts with merged results.

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?

States a specific verb and resource ('Search the iOS App Store and Google Play') and names the output artifact ('apps and their ids'), plus the extension to wordpress/chrome/steam. An agent can distinguish this lookup tool from siblings like get_app_details without opening the schema.

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?

'Use this FIRST when you only know an app name or a category' gives a clear entry-point condition relative to the detail-oriented siblings. It stops short of an explicit when-not or naming a specific alternative tool, so it is strong but not complete routing guidance.

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.