SEO GSC Wizard MCP

Set the IndexNow API key

update_indexnow_settings

Destructive

Sets, generates, rotates or clears the IndexNow API key for a property. The key is what search engines use to verify submissions from submit_indexnow_urls. To set IndexNow up, pass generateKey: true: a valid key is created and returned with keyFileUrl and keyFileContent. IMPORTANT: the site owner must then publish keyFileContent as a plain-text file at keyFileUrl (at the root of every host whose URLs will be submitted), or every submission is discarded. generateKey refuses to replace an existing key; to rotate, pass clear: true first. You can also pass your own indexnowApiKey (8-128 letters, digits and hyphens), for example one whose key file the site already publishes: the file is checked right after saving and keyFileVerified reports the result (true = ready to submit). Pass clear: true to remove the key, which disables IndexNow submissions for the property. Reading the key back later (get_indexnow_settings) only ever returns it masked.

Input Schema

Name	Required	Description
`clear`	No	Remove the stored key instead of setting one. Disables IndexNow submissions.
`siteUrl`	Yes
`generateKey`	No	Create a new valid key and return the key file to publish. Only when the property has no key yet; clear the old key first to rotate.
`indexnowApiKey`	No	The new key. Omit when using generateKey or clear.

Output Schema

Name	Required	Description	Default
`cleared`	No
`siteUrl`	No
`nextStep`	No
`generated`	No
`keyFileUrl`	No
`keyFileUrls`	No
`keyFileError`	No
`keyFileContent`	No
`keyFileVerified`	No
`indexnowApiKeySet`	No
`indexnowApiKeyMasked`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed8 schema fields changedOct 10, 2026

addedInput schema / properties / generateKey

Added value: +{
+  "default": false,
+  "description": "Create a new valid key and return the key file to publish. Only when the property has no key yet; clear the old key first to rotate.",
+  "type": "boolean"
+}

changedInput schema / properties / indexnowApiKey / description

Previous value: -"The new key. Omit together with clear: true to remove the current key."New value: +"The new key. Omit when using generateKey or clear."

addedOutput schema / properties / generated

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

addedOutput schema / properties / keyFileContent

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

addedOutput schema / properties / keyFileError

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

addedOutput schema / properties / keyFileUrl

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

addedOutput schema / properties / keyFileUrls

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / keyFileVerified

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

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say destructive/open-world/non-readonly; the description adds the real operational consequences: submissions are discarded unless keyFileContent is published at keyFileUrl on every host, clearing disables submissions for the property, generateKey will not overwrite, the key file is checked on save with keyFileVerified reporting readiness, and reads are always masked.

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-loaded with the purpose and the core generateKey workflow, then the publish requirement in caps, then edge cases. It is dense and slightly long, but every sentence carries actionable information rather than filler.

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?

Covers the full lifecycle (set/generate/rotate/clear), the required follow-up action, verification feedback, and the read path, and it names the return fields. An output schema exists, so return-value exposition is not owed here; nothing needed to call this 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 75% and the description enriches the remaining ambiguity: it explains what generateKey returns (keyFileUrl, keyFileContent), what clear does to submissions, and frames indexnowApiKey as a key whose file the site already publishes (with verification). The 8-128 alphanumeric/hyphen constraint is already in the schema, so the description does not need to restate it.

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 specific verbs (sets, generates, rotates, clears) and the exact resource (the IndexNow API key for a property), which immediately distinguishes it from get_indexnow_settings (read) and submit_indexnow_urls (submission). An agent can place it without opening the 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 explicit branching guidance: use generateKey:true for first-time setup, generateKey refuses to replace an existing key so pass clear:true first to rotate, pass clear:true to remove, or supply your own indexnowApiKey. It also routes reads to get_indexnow_settings, so when/when-not/alternative are all 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?