Skip to main content
Glama

Competitor keyword ideas

get_competitor_keywords
Read-only

Derives 1–3 word candidates from the top 10 competitors ranking for a keyword and returns those with popularity > 5, highest first. Pass your appStoreId to exclude your own app. Counts toward the research quota. Defaults to 20 keywords (max 100). Use nextOffset for more; null means the last page. Each page counts as a research call: pass limit: 100 to get everything in one call. Current metrics only, no difficulty history.

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": "get_competitor_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYes
limitNoResults per page (max 100)
storeNous
offsetNoStart at this offset; use nextOffset from the previous response
platformNoiphone
appStoreIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 20,
      +  "description": "Results per page (max 100)",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Start at this offset; use nextOffset from the previous response",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond by disclosing quota consumption per page, pagination termination ('null means the last page'), the popularity > 5 filtering threshold, sort order, and that metrics are current-only with no difficulty history. These are exactly the behavioral facts an agent needs before calling.

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?

Dense but zero-waste: output shape and filter come first, then cost/quota, then pagination, then a caveat about metric depth. Every sentence carries information an agent would otherwise have to guess.

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 six parameters, no output schema, and thin annotations, the description does substantial work: it covers cost model, pagination, filtering, ordering, and self-exclusion. The main remaining gap is the meaning and defaults of 'store' and 'platform', which affect which App Store catalog is queried.

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 only 33%, so the description must carry weight; it does explain appStoreId's purpose (exclude your own app), offset/nextOffset null-termination, and the limit default/max. However, 'store' and 'platform' parameters are left completely undefined in both schema and description, and 'term' is only implied.

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 ('derives') and a specific resource ('1–3 word candidates from the top 10 competitors ranking for a keyword'), plus the filter ('popularity > 5') and ordering ('highest first'). This is clearly distinguishable from siblings like get_app_keywords and get_keyword_suggestions.

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?

Gives actionable usage guidance: pass appStoreId to exclude your own app, use nextOffset for more pages, and pass limit: 100 to avoid multiple research-call charges. It does not explicitly contrast with sibling keyword tools (e.g. get_keyword_suggestions), so the when-to-use-vs-alternative dimension is implied rather than stated.

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