IndexNow Submit

Submit sitemap URLs to IndexNow

indexnow_submit

Idempotent

Submits a site's URLs to every IndexNow search engine. Use it when the user asks to submit their sitemap or changed pages to Bing, Yandex or IndexNow, for example "submit the pages that changed this week on example.com". Pass site and key; optional changed_since, path_prefix, sitemap or urls. It reads the key file first and sends nothing unless the file holds exactly the key. Then it posts the URLs to Microsoft Bing, Yandex, Seznam.cz, Naver, Yep, Amazonbot and returns each engine's status, HTTP code and meaning. At most 10,000 URLs per submit; pass batch 2, 3 and on for the rest. Limits: one submit per site every 60 seconds, and the same batch once every 5 minutes. Accepted is not indexed. Do not use it for a site the user does not own.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	Yes	The site's IndexNow key. Its key file must be live: nothing is sent unless the file holds exactly this key.
`site`	Yes	The site's domain or address, such as example.com or https://www.example.com. A bare domain means https. One host per call: www.example.com and example.com are different hosts.
`urls`	No	Optional list of URLs to send instead of the sitemap, all on the site's host. At most 10,000.
`batch`	No	Optional, default 1. When more URLs qualify than one submit takes, batch 2 is the next slice of the newest-first list, and so on; urls.batches says how many there are.
`engines`	No	Optional subset of engines. Default: all 6 (bing, yandex, seznam, naver, yep, amazonbot).
`sitemap`	No	Optional sitemap or sitemap index address. Without it the Sitemap lines of robots.txt are used, then /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml. Gzip files work.
`max_urls`	No	Optional URLs per submit, default 10,000. When more URLs qualify, the newest lastmod goes first and the rest wait for the next batch.
`path_prefix`	No	Optional path start, such as /blog/. Only URLs under it.
`key_location`	No	Optional https address of the key file when it is not at /<key>.txt. It must be on the same host and end in .txt; it then covers only URLs in its folder and below.
`changed_since`	No	Optional YYYY-MM-DD. Only sitemap URLs whose lastmod is on or after this day; URLs with no lastmod are left out.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`host`	Yes
`site`	Yes
`urls`	Yes
`as_of`	Yes
`reason`	Yes
`ad_line`	Yes
`engines`	Yes
`sitemap`	Yes
`summary`	Yes
`key_file`	Yes
`protocol`	Yes
`url_list`	No
`next_step`	Yes
`submitted`	Yes
`acceptance_note`	Yes
`retry_after_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only flag openWorld/idempotent/non-destructive; the description adds unique context beyond them: it verifies the key file first and sends nothing unless the file holds exactly the key, returns per-engine status/HTTP code/meaning, notes batch limits of 10,000 URLs, rate limits (60s per site, 5min per batch), and cautions that 'Accepted is not indexed.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and useful, but the description is dense and multi-sentence, mixing usage, behavior, limits, and caution into a single paragraph. Some pruning would improve scannability without losing substance.

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

Completeness5/5

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

For a 10-parameter write tool with rich schema and an output schema, the description covers intent routing, the key-file precondition, return format expectations, batching, rate limits, and ownership caveats – complete enough for correct invocation.

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 coverage is 100% so baseline is 3, but the description reinforces key/site usage and explains batching semantics ('pass batch 2, 3 and on for the rest'). Comparative to the schema, it adds only mild extra meaning, so a 4 is appropriate.

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 the specific action (submits URLs to every IndexNow search engine) and immediately maps to user intents like 'submit their sitemap or changed pages to Bing, Yandex or IndexNow', including an example utterance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use (user asks to submit sitemap/changed pages), names target engines, and adds a clear when-not-to-use exclusion: 'Do not use it for a site the user does not own.'

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

All IndexNow Submit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.