Skip to main content
Glama

SteadyScrape SEO Data

Rank check for up to 10 keywords (Google)

rank_check
Read-onlyIdempotent

Where one domain ranks on live Google for up to 10 keywords in one country: best position, ranking URL and the top 3 domains for each keyword, plus SERP features. Same data and price as google_serp, billed per 10 results of depth for each keyword that returns results.

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": {
      "keywords": "<keywords>",
      "target_domain": "<target_domain>"
    },
    "name": "rank_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoResults checked per keyword: 10-100 (default 10).
deviceNoDefault desktop.
countryNo2-letter country code (US, GB, DE...) or English name. Default US.
keywordsYes1-10 search queries.
languageNoLanguage code, e.g. en, es, de. Default en.
target_domainYesDomain to find, e.g. example.com (subdomains count).

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 declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: live Google data, a hard cap of 10 keywords, and an explicit billing rule (per 10 results of depth for each keyword that returns results). It does not discuss failure/zero-result handling, but the cost model disclosure is genuinely useful.

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 sentences, front-loaded with what the tool does and what it returns, then cost. Dense but every clause carries information; nothing is redundant filler.

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

Completeness4/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 enumerates the return shape (position, ranking URL, top 3 domains, SERP features) and discloses pricing, which is enough to call the tool correctly. The remaining gap is the lack of guidance on choosing between this and google_serp given their stated equivalence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns an increment by tying the depth parameter to cost ('billed per 10 results of depth for each keyword'), which the schema does not convey. The 'one country' phrasing reinforces the scope of country/keywords but adds little 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?

States a specific operation ('Where one domain ranks on live Google for up to 10 keywords in one country') and enumerates the returns: best position, ranking URL, top 3 domains, SERP features. An agent can tell what it produces, though the 'same data as google_serp' remark blurs how it differs from that sibling rather than sharpening it.

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 usage context is implied by the framing (one target domain, up to 10 keywords, one country), but there is no explicit 'use this when' or 'use google_serp instead when' guidance. Mentioning that it shares data and price with google_serp without a discriminator leaves the routing decision to inference.

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