Skip to main content
Glama

ADS Beast

seo_keyword_rank_check

Read-only

A site's Google position for one keyword with the matched URL, SERP features and the top ten.

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>",
      "domain": "<domain>"
    },
    "name": "seo_keyword_rank_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
glNoCountry code of the search.
hlNoInterface language of the search.
domainYesDomain without scheme.
keywordYesTarget search query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results include the matched URL, SERP features, and the top ten, which is useful because no output schema exists, but it says nothing about credit cost, rate limits, or what happens when a keyword has no ranking.

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?

It is a single front-loaded sentence with no wasted wording. It is slightly telegraphic ('the top ten' without saying top ten what), but efficient overall.

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 usefully names what comes back, which is the main completeness win. However, for an open-world SERP lookup that likely consumes external credits, the absence of usage conditions, failure behavior, and sibling routing leaves meaningful gaps.

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 description coverage is 100%, so gl, hl, domain, and keyword are already documented. The description reinforces that 'keyword' is a single query and 'domain' refers to the site, but adds no syntax, format, or defaulting guidance beyond the schema.

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 verb and resource: retrieving a site's Google position for one keyword, along with the matched URL, SERP features, and the top ten results. This is clear enough to distinguish a single-keyword lookup from bulk tools like seo_keywords_track, but it never explicitly contrasts itself with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives such as seo_rank_changes or seo_keywords_track, nor any stated prerequisites. The phrase 'for one keyword' implies a single-query scope, but an agent must infer whether to call this or a tracking tool.

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.