Skip to main content
Glama

Get app keywords

get_app_keywords
Read-only

Tracked keywords of an app with latest metrics, 20 per page by default. Use nextOffset for more.

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": {
      "appId": "<appId>"
    },
    "name": "get_app_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesLocal app id from list_apps, not the App Store ID
limitNoResults per page (max 100)
offsetNoStart at this offset; use nextOffset from the previous response

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

B3.4/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's contribution is the pagination behavior — 20 per page by default and continuation via nextOffset. That is useful, but it largely restates the schema defaults and gives no detail on what the metrics payload contains or how large the result set can be.

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?

Two short sentences, front-loaded with the resource and its content, then the pagination caveat. Nothing is padded, though the phrasing is telegraphic enough that 'latest metrics' is left unexplained.

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

Completeness3/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 carries responsibility for describing the return shape, and 'latest metrics' is the only hint about what fields come back. It is adequate for a simple paginated read but leaves the agent guessing about the metric contents and total-count behavior.

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 coverage is 100%, so the schema already documents appId (local id, not App Store id), limit (max 100) and offset. The description's '20 per page by default' duplicates the schema default and adds no new meaning; baseline 3 applies. Minor ambiguity: it says nextOffset while the input parameter is named offset.

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?

The description names the resource precisely — an app's tracked keywords plus their latest metrics — which distinguishes it from siblings like get_competitor_keywords or get_keyword_history. The retrieval verb is implicit rather than stated, but an agent can still tell what the tool returns.

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: 'tracked keywords of an app' suggests this is for keywords already added via add_keywords, but the description never says when to prefer this over get_competitor_keywords or get_keyword_history. The pagination guidance ('Use nextOffset for more') is the only explicit operational instruction.

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