Check a URL's indexing status, crawl information, and overall health to diagnose SEO issues.
Inspect a URL to check its indexing status, crawl info, and health
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The URL of the property | |
| inspectionUrl | Yes | The fully-qualified URL to inspect | |
| languageCode | No | Language code for localized results (Google only) | |
| engine | No | The search engine (default: google) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description lacks disclosure of behavioral traits such as rate limits, permissions, or error handling. Only mentions what it checks without behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence of 12 words, no redundancy. Every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate but lacking: no output schema, and description does not mention what the inspection result contains. Could be more complete for a tool with 4 params.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for all 4 parameters. The tool description adds no extra semantics beyond the schema, so baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool inspects a URL for indexing status, crawl info, and health. However, it does not differentiate from similar siblings like inspection_batch or indexing_status.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage from 'indexing status, crawl info, health' but no explicit guidance on when to use this vs alternatives like inspection_batch or bing_url_info.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.