Inspect a URL's indexing and crawl status in Bing. Provides details on how Bing sees and processes the page for SEO analysis.
Get detailed indexing and crawl information for a URL in Bing
| Name | Required | Description | Default |
|---|---|---|---|
| siteUrl | Yes | The site URL | |
| url | Yes | The specific URL to inspect |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. It says 'detailed indexing and crawl information' but does not specify what is returned, permission requirements, or rate limits. Minimal behavioral disclosure.
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 10 words, front-loaded with verb and resource. No unnecessary words.
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?
No output schema, no annotations, and description only provides high-level purpose. Agent lacks information on return structure, pagination, or usage constraints. Incomplete for a tool with no structured guidance.
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 has 100% coverage with descriptions for both parameters (siteUrl: 'The site URL', url: 'The specific URL to inspect'). Description adds no extra meaning beyond what schema already provides, so baseline 3.
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 'Get detailed indexing and crawl information for a URL in Bing', specifying the verb (Get) and resource (indexing and crawl info for a URL). It distinguishes from siblings like bing_crawl_issues or inspection_inspect.
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?
No guidance on when to use this tool versus alternatives, such as bing_crawl_issues or bing_url_submit. No prerequisites or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.