Skip to main content
Glama

indexnow_generate_key

Generate a new IndexNow key to authenticate URL submissions; save the key in a .txt file at your site root for search engine verification.

Instructions

Generate a new IndexNow key. The key must be placed in a .txt file on your site root.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "indexnow_generate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNoKey length (8-128 characters, default 32)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that no server-side registration occurs and the key must be self-hosted, but it omits whether generating a key invalidates or overwrites a previously generated key, whether the key is stored by the service, and whether the .txt filename must match the key value.

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?

Two short sentences, front-loaded with the action and followed by the one operational requirement. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

For a simple single-parameter utility with no output schema, the definition is minimally viable. It still leaves open the practical detail most likely to cause failure: the required '{key}.txt' filename convention on the site root and whether the returned key is stable across calls.

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 coverage is 100% and the single 'length' parameter already documents its 8-128 range and default of 32. The description adds nothing beyond that, so the baseline of 3 applies.

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?

The description states a specific verb and resource ('Generate a new IndexNow key'), and the word 'new' implicitly separates it from indexnow_validate_key. It is clear what the tool produces, though it does not explicitly name the sibling it complements.

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?

The second sentence gives deployment context (the key must live in a .txt file at the site root), which implies when this step is needed before validation or submission. However, it never states when to use this versus indexnow_validate_key, nor whether an existing key should be reused instead of regenerated.

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