Murkuz SEO

Inspect_URL

What Google currently knows about one URL: index status, last crawl, the canonical Google actually chose versus the one you declared, robots and mobile usability. Cached for one hour per site and URL, because this API's quota is far tighter than Search Analytics' own; a repeated call within the hour returns the cached result rather than spending quota again.

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": {
      "site_id": "<site_id>",
      "url": "<url>"
    },
    "name": "Inspect_URL"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The exact page URL to inspect.
`site_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does meaningfully disclose behavior: a one-hour cache per site+URL and the reason (tighter quota than Search Analytics), plus that repeats within the hour return cached data instead of spending quota. It omits prerequisites such as whether site_id must be a verified Search Console property and what happens for URLs outside the property.

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-loaded with the payload summary, then a single supporting sentence on caching and quota. Dense and largely waste-free, though the quota rationale is slightly verbose for a definition.

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 and no annotations, the description helpfully enumerates the returned fields, which is the right compensation for a read-only inspection tool. The main gap is the unexplained site_id and unstated authentication/property-verification requirement for a 2-parameter tool.

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

Parameters2/5

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

Schema coverage is 50%: 'url' is documented in the schema, but 'site_id' has no description anywhere, and the description never clarifies what site_id is (a verified Search Console property identifier) or its accepted format. The phrase 'per site and URL' hints at scoping for caching but does not compensate for the undocumented parameter.

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 gives a specific verb+resource ('What Google currently knows about one URL') and enumerates exactly what is returned: index status, last crawl, canonical mismatch, robots, mobile usability. It is clear and concrete, though it only mentions the sibling Search Analytics for a quota comparison rather than as a routing alternative.

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 content listed (you call this when you need Google's index/crawl view of a single page), and the quota/caching note hints at cost-conscious usage, but there is no explicit when-to-use guidance or differentiation from siblings like Landing_Page_Diagnosis or SERP_Snapshot that an agent might otherwise pick.

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

All Murkuz SEO 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?