IndexNow Submit

Check IndexNow key file and sitemap

indexnow_check

Read-onlyIdempotent

Checks a site's IndexNow setup and submits nothing. Use it when the user asks whether their IndexNow key file works, which URLs would be submitted, or how to start with IndexNow, for example "is my IndexNow key set up on example.com?". Pass site and key; leave key out to get a new key and the file to publish. Returns the key file verdict with the exact fix, the sitemap found (robots.txt, index, gzip), how many URLs qualify, why others are left out, a sample, and the next step. Protocol: https://www.indexnow.org/documentation. Do not use it for a site the user does not own, or to read a site's content.

Input Schema

TableJSON Schema

Name	Required	Description
`key`	No	The site's IndexNow key, 8 to 128 letters, digits or dashes. Leave it out to get a new key and the exact file to publish.
`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.
`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
`ready`	Yes
`ad_line`	Yes
`engines`	Yes
`new_key`	Yes
`sitemap`	Yes
`key_file`	Yes
`protocol`	Yes
`url_list`	No
`next_step`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds valuable non-schema context: it previews the diagnostic return shape (verdict, exact fix, sitemap sources, qualifying URL count, sample, next step) and notes that omitting the key yields a new key and file to publish. It stops short of stating auth needs or rate limits, so a 4 rather than a 5.

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?

Front-loads the purpose and the when-to-use clause before the long return-value inventory, and the doc link plus the closing exclusion are earned. The middle sentence listing six return elements is dense but relevant; nothing is truly wasted.

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 9-parameter diagnostic tool, the description covers purpose, triggers, exclusions, the key-omission behavior, and a preview of what comes back, while the output schema and annotations carry the rest. Nothing an agent needs in order to call it correctly is missing.

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 adds meaning beyond the schema by explaining the key-omission branch ('leave key out to get a new key and the file to publish') and by framing site/key as the two things to pass. The batch/max_urls/path_prefix/changed_since interplay is left to the schema's own descriptions.

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 and resource ('Checks a site's IndexNow setup') and immediately disambiguates from the sibling indexnow_submit with 'submits nothing'. An agent can tell it apart from indexnow_submit 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 Guidelines5/5

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

Gives concrete trigger conditions (user asks whether the key file works, which URLs would be submitted, or how to start) with a sample utterance, plus explicit exclusions: not for sites the user does not own and not for reading site content.

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.