Submit URLs to Bing and Yandex via IndexNow API to notify search engines of content updates and changes.
Submit URLs via IndexNow API (Bing, Yandex, etc.)
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | The host/domain where URLs are located (e.g., www.example.com) | |
| key | Yes | The IndexNow key generated for this host | |
| keyLocation | No | Optional URL of the key file (if not at host root) | |
| urlList | Yes | List of absolute URLs to notify IndexNow about |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description fails to disclose behavioral traits like rate limits, idempotency, required permissions, or side effects. Only states the action without any safety or constraint 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?
Extremely concise single sentence; front-loaded with purpose. However, it omits necessary detail, slightly reducing effectiveness.
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?
For a tool with 4 parameters, no output schema, and no annotations, this description is critically incomplete. Lacks info on return values, failure modes, prerequisites, and integration context.
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 parameters, so description adds no further value. Baseline score of 3 applies.
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?
Description clearly states verb 'Submit' and resource 'URLs via IndexNow API', and names specific services (Bing, Yandex). Differentiates from siblings like bing_url_submit by referencing the IndexNow protocol.
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 vs related siblings like bing_url_submit or indexing_submit_url. Usage context is only implied by the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.