Skip to main content
Glama

SEO Rank Fixer

Keyword explorer

keyword_explorer
Read-onlyIdempotent

Looks up any keyword in Google's data for one country: monthly searches (with the last 12 months), keyword difficulty (0-100), search intent, up to 100 related keyword ideas with their searches, difficulty and intent, and who ranks in Google's top 10 now (the site and its saved competitors marked when siteId is given). What is included depends on the plan. Each new lookup uses one of the workspace's daily lookups; a keyword looked up in the same country in the last 30 days is answered from the store and does not count.

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": {
      "keyword": "<keyword>"
    },
    "name": "keyword_explorer"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdNoA site id from list_sites, to use its country and mark it and its competitors in the top 10. Optional.
countryNoCountry code: usa, gbr, can, aus, ind, irl, nzl, zaf, sgp, deu, aut, che, fra, bel, nld, esp, mex, ita, prt, bra, swe, dnk, pol, jpn, are, sau. Optional: the site's country, else usa.
keywordYesThe search to look up, e.g. emergency plumber.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, and the description is consistent with them. It adds real context the annotations cannot: per-call quota consumption, the 30-day country-scoped cache, and that the returned fields depend on the plan. It still omits failure behavior (e.g. what happens when the daily quota runs out) and any latency expectations.

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?

Front-loads the substantive payload list before the operational caveats, with no filler sentences. It is a dense single paragraph, however, and the plan-dependence clause is easy to skim past rather than structurally separated.

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 carries the burden of describing return values, and it does so completely: searches with 12-month history, 0-100 difficulty, intent, related keywords, and current top-10 rankers. Combined with the quota and caching rules, an agent has everything needed to decide to call and interpret results.

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 all three parameters, including the country code list, its default-to-site-else-usa behavior, and siteId's default and marking role. The description reinforces that lookups are scoped to a single country and that siteId marks the site plus saved competitors, but adds little syntax or meaning beyond the schema text, so the baseline 3 applies.

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 ("looks up any keyword in Google's data for one country") and enumerates the returned data points: monthly searches, difficulty, intent, up to 100 related ideas, and top-10 rankers. An agent can tell this is a keyword-research lookup rather than a site audit or reporting tool without opening the schema.

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 meaningful call-context guidance by disclosing that each new lookup consumes one of the workspace's daily lookups while a repeat lookup in the same country within 30 days is served from the store for free, which directly informs when calling is cheap. It does not explicitly exclude or route to a sibling tool, so it falls short of full when/when-not guidance.

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.