Skip to main content
Glama

indexnow_submit_url

Submit a single URL through IndexNow to request instant indexing by multiple search engines.

Instructions

Submit a single URL via IndexNow for instant indexing by multiple search engines.

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

Input Schema

NameRequiredDescriptionDefault
keyNoThe IndexNow key (uses INDEXNOW_KEY env var if not provided)
urlYesThe URL to submit
keyLocationNoCustom key file location URL (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only the high-level benefit ('instant indexing by multiple search engines') and says nothing about key authentication requirements (the key param uses an env var fallback), rate limits or quotas, whether submission guarantees crawling, or failure behavior — significant gaps for a network-facing mutation tool.

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?

A single sentence with no filler, front-loaded with the verb and scope, and ending on the payoff. Nothing repeats structured data unnecessarily and nothing could be trimmed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-required-parameter tool with full schema coverage this is close to adequate, but with no output schema the description should say what a call returns (submission status, per-engine results, errors), and it omits any quota or key-setup context that would prevent failed calls.

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 100%, so the schema already defines url, key and keyLocation including the env-var fallback, which sets the baseline at 3. The description adds a small amount by reinforcing that exactly one URL is submitted per call rather than a list, which clarifies the required parameter's expected shape.

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 ('Submit'), a specific resource ('a single URL'), the protocol ('via IndexNow'), and the effect ('instant indexing by multiple search engines'). The word 'single' cleanly separates it from the sibling indexnow_submit_batch, so an agent can route without opening either 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 'single URL' framing, which suggests the batch tool for many URLs, but the description never explicitly says when to prefer it, nor does it mention the sibling bing_submit_url alternative or any prerequisite such as possessing a key. The agent must infer routing from the tool name alone.

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