SEO GSC Wizard MCP

List IndexNow submissions

list_indexnow_submissions

Read-only

Use this when the user asks which URLs were sent to IndexNow and how engines answered. Returns the IndexNow submission history for a property: URL, response code, source (such as manual, paste or mcp) and timestamp. Newest first (submitted_at, then url, descending); total counts all stored rows. A 202 means accepted, key validation pending, not delivered. Not for sending URLs: use submit_indexnow_urls.

Input Schema

Name	Required	Description	Default
`limit`	No
`siteUrl`	Yes

Output Schema

Name	Required	Description
`total`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`nextStep`	No
`ordering`	No
`sortedBy`	No
`sortOrder`	No
`thenOrder`	No
`submissions`	No
`emptyBecause`	No
`methodLimits`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

Changed13 schema fields changedOct 18, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

changedOutput schema / properties / submissions / items / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / submissions / items / properties / response_code / $ref
```
Added value: +"#/properties/total"
```
removedOutput schema / properties / submissions / items / properties / response_code / type
```
Removed value: -[
-  "number",
-  "null"
-]
```

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / total

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

First observedOct 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only and closed-world safety, and the description adds real behavioral context on top: sort order (submitted_at then url, descending), that total counts all stored rows rather than the page, and the semantic meaning of a 202 ('accepted, key validation pending, not delivered') — a nuance the agent could not infer from structured fields.

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?

Front-loaded with the use trigger, then result fields, ordering, total semantics, and the sibling exclusion — every sentence carries distinct information with no restatement of the name or title.

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?

Despite having an output schema, the description still supplies the interpretive layer an agent needs (sort order, total semantics, 202 meaning). For a two-parameter read tool with full annotations, nothing material for correct invocation is missing.

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 0%, so the description must carry parameter meaning. It implies siteUrl via 'for a property' and clarifies that total is independent of the returned slice, but it never mentions the limit parameter's default of 100 or its 1-500 bounds. Useful hints, incomplete compensation for the coverage gap.

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 ('Returns the IndexNow submission history for a property') and enumerates the returned fields (URL, response code, source, timestamp). It explicitly distinguishes itself from submit_indexnow_urls, 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 Guidelines5/5

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

Opens with an explicit use trigger ('Use this when the user asks which URLs were sent to IndexNow and how engines answered') and closes with an explicit exclusion plus the named alternative ('Not for sending URLs: use submit_indexnow_urls'). Both the when and the when-not are covered.

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

All SEO GSC Wizard MCP 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.

Resources

Need Help?