Skip to main content
Glama

indexnow_list_engines

Retrieve supported search engines and their API endpoints for URL indexing through IndexNow.

Instructions

List all supported IndexNow search engines and their API endpoints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the indexnow_list_engines tool, which generates a list of supported search engines and their API endpoints.
    server.tool(
      "indexnow_list_engines",
      "List all supported IndexNow search engines and their API endpoints.",
      {},
      async () => {
        let output = `## Supported IndexNow Engines\n\n`;
        output += `| Engine | Endpoint |\n|--------|----------|\n`;
        for (const [name, url] of Object.entries(INDEXNOW_ENDPOINTS)) {
          output += `| ${name} | ${url} |\n`;
        }
    
        output += `\n### Google Indexing API\n`;
        output += `| Service | Endpoint |\n|---------|----------|\n`;
        output += `| Google Indexing API | ${GOOGLE_INDEXING_API_URL} |\n`;
        output += `| Google Batch API | ${GOOGLE_BATCH_URL} |\n`;
    
        output += `\n### Notes\n`;
        output += `- **IndexNow** is supported by Bing, Yandex, Naver, and Seznam\n`;
        output += `- **Google** has its own Indexing API (requires service account + OAuth2)\n`;
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully indicates this is a read operation returning engine configurations, but omits details about network requirements, caching behavior, rate limits, or authentication needs that would help an agent understand the operational constraints.

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?

The description consists of a single, efficient sentence with nine words. It is appropriately front-loaded with the action verb and contains no redundant or wasted language, making it ideal for quick comprehension by an agent.

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

Completeness4/5

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

Given the low complexity (zero inputs, no output schema, no annotations), the description adequately covers the functional scope by specifying what data it returns (engines and endpoints). While an output schema would be ideal, the description sufficiently compensates by clarifying the return value for this simple discovery tool.

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?

The tool has zero parameters and the schema is an empty object. Per evaluation guidelines, 0-parameter tools receive a baseline score of 4. The description appropriately does not mention parameters since none exist, requiring no additional semantic clarification beyond what the trivial schema provides.

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?

The description uses a specific verb ('List') and clearly identifies the resource ('IndexNow search engines and their API endpoints'). It effectively distinguishes this tool from its siblings (indexnow_submit, indexnow_submit_sitemap, etc.) by positioning it as a discovery/listing operation rather than an action/submission operation.

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

Usage Guidelines2/5

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

The description states what the tool does but provides no explicit guidance on when to invoke it versus alternatives. It does not indicate, for example, that this should be called before indexnow_submit to discover available endpoints, or whether the results are static reference data.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sharozdawa/indexnow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server