Skip to main content
Glama

Most searched keywords

get_most_searched_keywords
Read-only

One page of the most searched keywords in a store, optionally for an App Store category id (e.g. 6013). Check month: data can be from an earlier month. Counts toward the research quota. Defaults to 20 keywords per page (max 100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_most_searched_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNoResults per page (max 100)
storeNous
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +20
    • addedInput schema / properties / limit / description
      Added value: +"Results per page (max 100)"
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds value: it warns that the call consumes research quota, and that returned data may be from an earlier month. Those are behavioral traits an agent cannot infer from annotations or schema. It omits return-shape details, but no output schema exists to compensate.

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?

Three short sentences with the main purpose front-loaded and no filler. The `month` instruction is the one sentence that does not earn its place, since it points at a parameter the tool does not accept.

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?

For a read-only, four-parameter listing tool with no output schema, the description covers pagination, quota cost, freshness, and category filtering reasonably well. It leaves `store` and `page` undefined and introduces a phantom `month` control, so an agent still has open questions before calling it.

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?

Coverage is only 25% (only `limit` is documented in-schema), so the description should compensate more. It does add a useful concrete format example for `category` (e.g. 6013) and restates the 20/100 paging limit, but it never explains `store` (country code) or `page`, and it tells the agent to 'Check `month`' even though no such parameter exists in the schema, which is actively confusing.

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 states a specific resource and scope: 'one page of the most searched keywords in a store, optionally for an App Store category id.' That is clearly distinct from siblings like get_keyword_popularity or get_keyword_suggestions, though it never names an alternative explicitly.

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 implied (browse top searched keywords globally or within a category) and it adds one real usage caveat: verify the month because data may be stale. However, it gives no when-not guidance and does not distinguish itself from sibling keyword tools such as get_keyword_popularity or get_competitor_keywords.

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