Skip to main content
Glama

Keyword suggestions

get_keyword_suggestions
Read-only

Keyword ideas for an App Store app with popularity and difficulty for the selected platform. 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": {
      "appStoreId": "<appStoreId>"
    },
    "name": "get_keyword_suggestions"
  }
}

Input Schema

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

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.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavior the agent can't infer: quota consumption ('counts toward the research quota'), per-page cost ('each page counts as a research call'), and a scope limit ('Current metrics only, no difficulty history'). The quota-cost disclosure is particularly valuable for an agent deciding page size.

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?

Five short sentences, front-loaded with what it returns, then quota cost, then pagination mechanics, then scope caveat. No filler; every clause carries operational information the agent needs before spending a research call.

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 tells the agent that results carry popularity and difficulty scores and an offset/nextOffset page marker, and it warns about billing per page. The remaining gap is the undocumented highPopularity filter and the unclear meaning of 'difficulty' as a metric, which the agent cannot act on without guessing.

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 33%, so description must compensate, and it does for three of six: limit (default 20, max 100), offset (via nextOffset and the null-terminates signal), and platform. It still leaves store, appStoreId, and especially highPopularity (a default-true boolean with no description anywhere) unexplained, so the compensation is partial.

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 ('keyword ideas for an App Store app') plus the returned metrics (popularity and difficulty) and the platform scoping. This clearly separates it from siblings like get_keyword_popularity (single-metric lookup), get_keyword_history (time series), and get_most_searched_keywords (not app-anchored).

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?

Gives strong operational guidance for pagination ('use nextOffset for more; null means the last page', 'pass limit: 100 to get everything in one call'), but never says when to pick this over get_keyword_popularity, get_competitor_keywords, or get_most_searched_keywords. Usage direction is present for how to call, absent for when to choose it.

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