Skip to main content
Glama

Keyword research

keyword_research

For one topic: search volume, CPC and difficulty for it and its related searches, the top 10 Google results (and where you rank), People Also Ask, up to 15 more searches around it (ideas, each with volume and difficulty; winnable is difficulty 30 or under, which a young site can reach the top 10 for), and the pages Perplexity cites with the brands it names. Pick a winnable idea with real volume over a hard one with more. Costs $0.06 from the balance, charged only when it returns. Nothing is charged when the data comes back empty.

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": {
      "topic": "<topic>"
    },
    "name": "keyword_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesA keyword or a buyer question

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already disclose that this is not read-only and is open-world, so the safety profile is partly covered. The description adds non-obvious behavior the annotations cannot: a $0.06 charge from the balance, billed only on a successful return, and no charge on empty results. It also defines the 'winnable' threshold (difficulty 30 or under, reachable by a young site).

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?

Scope is front-loaded ('For one topic'), followed by a dense but readable enumeration of outputs, a decision heuristic, and the billing rule. Every sentence carries information, though the output enumeration is long enough to slightly strain scanability.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return-value burden and it does: it lists each result section, explains the meaning of the `ideas` fields and the `winnable` flag, and states cost and charging conditions. An agent can decide, budget, and interpret results without further documentation.

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%, with the single parameter already documented as 'A keyword or a buyer question' with length bounds, so the schema carries the field-level meaning. The description reinforces single-topic scope ('For one topic') but adds no format or phrasing guidance beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and enumerates exactly what is returned: search volume, CPC, difficulty, top 10 Google results with rank position, People Also Ask, up to 15 related searches, and Perplexity citations. Scope is pinned down with 'For one topic'. It does not name a sibling tool it is not, so an agent must infer the distinction from the 'ideas'/'research' names alone.

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?

The guidance 'Pick a winnable idea with real volume over a hard one with more' tells the agent how to interpret and act on results, and the price note implies this is a paid call to use sparingly. However, there is no explicit when-to-use versus when-not, and no named alternative for cases where a cheaper or broader search fits.

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