Skip to main content
Glama

indexnow_submit_batch

Submit up to 10,000 URLs in one batch via IndexNow to request instant indexing for a host, using an optional key or key location.

Instructions

Submit multiple URLs via IndexNow (max 10,000 per submission) for instant indexing.

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": {
      "host": "<host>",
      "urls": "<urls>"
    },
    "name": "indexnow_submit_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe IndexNow key (uses INDEXNOW_KEY env var if not provided)
hostYesThe hostname for all URLs
urlsYesArray of URLs to submit (max 10,000)
keyLocationNoCustom key file location URL (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no error/partial-failure behavior, no rate limits or submission quota, no statement about whether resubmitting URLs is idempotent, and no indication that the host must match the key file. 'Instant indexing' is an unverifiable marketing claim rather than a behavioral trait.

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?

A single front-loaded sentence with no filler; the limit and the benefit are packed in efficiently. It is arguably too terse for a submission tool, but there is no wasted wording.

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

Completeness2/5

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

For a four-parameter write-style submission tool with no annotations and no output schema, the description leaves too much out: prerequisite key setup, host/URL domain matching, quota and rate limits, and what a response or failure looks like. The schema covers parameter naming but nothing about operational context.

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

Parameters3/5

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

Schema description coverage is 100%, including the 10,000 cap that the description merely repeats, so the baseline of 3 applies. The description adds no meaning beyond the schema — it does not explain the relationship between host and urls (e.g., all URLs must belong to that host) or when keyLocation is needed.

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?

States a specific verb and resource ('Submit multiple URLs via IndexNow') plus a hard limit and the outcome ('instant indexing'). The word 'multiple' implicitly separates it from the singular indexnow_submit_url sibling, but the description never names that sibling or the bing_submit_url_batch alternative explicitly.

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 only implied by the name/description: batch submission. There is no explicit when-to-use/when-not, no mention that a valid IndexNow key is a prerequisite (despite indexnow_generate_key and indexnow_validate_key being available), and no guidance on choosing this over bing_submit_url_batch.

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