RanklyBee

Check whether URLs are indexed

inspect_urls

Run Google URL Inspection on up to 10 URLs of the Project's property and return each one's indexing verdict, coverage state and canonical; results are kept. With skipCheckedWithinDays, URLs inspected that recently return their stored result. Google allows 2,000 inspections per property per day.

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": {
      "projectId": "<projectId>",
      "urls": "<urls>"
    },
    "name": "inspect_urls"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes
`projectId`	Yes
`skipCheckedWithinDays`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the external quota ('2,000 inspections per property per day'), that results are stored and re-served, and that skipCheckedWithinDays returns stored results rather than fresh inspections. It stops short of explaining why readOnlyHint is false in terms of side effects (writes/cache population), though 'results are kept' hints at persistence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and scope, then the caching clause and the quota. No filler or repetition of the schema.

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?

No output schema exists, and the description lists the returned fields (verdict, coverage state, canonical), which is exactly what is needed. It omits edge-case behavior such as partial failures within a batch of URLs, non-property URLs, or what the stored-result shape looks like within the skip window.

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 description coverage is 0%, so the description must carry the load and does: it fixes the urls cap at 10 and explains skipCheckedWithinDays as a cache-reuse window. projectId is only indirectly explained via 'the Project's property' and no format or ownership constraints are given.

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 ('Run Google URL Inspection on up to 10 URLs of the Project's property') plus the returned payload (indexing verdict, coverage state, canonical). No sibling tool performs per-URL inspection, so an agent can distinguish it from get_sitemap_urls or get_search_console_report 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 Guidelines3/5

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

Usage is implied by the purpose and the skipCheckedWithinDays clause tells the agent when cached results are reused, but there is no explicit when-to-use/when-not distinction against alternatives such as get_sitemap_urls or the search console tools. The daily quota is mentioned but framed as a fact, not as a budgeting rule for batching.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All RanklyBee tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?