Skip to main content
Glama

google_indexing_status

Check when a URL was last submitted to Google for indexing via the Google Indexing API to monitor indexing notification status.

Instructions

Check the indexing notification status of a URL via Google Indexing API. Shows when the URL was last submitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to check indexing status for
access_tokenYesGoogle OAuth2 access token

Implementation Reference

  • The tool handler for 'google_indexing_status' which calls the checkIndexStatus function.
    async ({ url, access_token }) => {
      const result = await checkIndexStatus(url, access_token);
    
      let output = `## Indexing Status\n\n`;
      output += `**URL:** ${result.url}\n`;
      if (result.error) {
        output += `**Error:** ${result.error}\n`;
      } else {
        output += `**Last Notification:** ${result.lastCrawled || "Never"}\n`;
        output += `**Type:** ${result.type || "Unknown"}\n`;
      }
    
      return { content: [{ type: "text" as const, text: output }] };
    }
  • The implementation function 'checkIndexStatus' that performs the API request to Google Indexing API.
    async function checkIndexStatus(
      url: string,
      accessToken: string
    ): Promise<{ url: string; lastCrawled?: string; type?: string; error?: string }> {
      try {
        const response = await fetch(
          `https://indexing.googleapis.com/v3/urlNotifications/metadata?url=${encodeURIComponent(url)}`,
          {
            headers: { Authorization: `Bearer ${accessToken}` },
            signal: AbortSignal.timeout(15000),
          }
        );
    
        if (!response.ok) {
          const data = await response.json();
          return { url, error: data.error?.message || `HTTP ${response.status}` };
        }
    
        const data = await response.json();
        return {
          url,
          lastCrawled: data.latestUpdate?.notifyTime || data.latestRemove?.notifyTime,
          type: data.latestUpdate ? "URL_UPDATED" : data.latestRemove ? "URL_DELETED" : "UNKNOWN",
        };
      } catch (error) {
        return {
          url,
          error: error instanceof Error ? error.message : "Unknown error",
        };
  • src/index.ts:283-304 (registration)
    Registration of the 'google_indexing_status' tool.
    server.tool(
      "google_indexing_status",
      "Check the indexing notification status of a URL via Google Indexing API. Shows when the URL was last submitted.",
      {
        url: z.string().url().describe("URL to check indexing status for"),
        access_token: z.string().describe("Google OAuth2 access token"),
      },
      async ({ url, access_token }) => {
        const result = await checkIndexStatus(url, access_token);
    
        let output = `## Indexing Status\n\n`;
        output += `**URL:** ${result.url}\n`;
        if (result.error) {
          output += `**Error:** ${result.error}\n`;
        } else {
          output += `**Last Notification:** ${result.lastCrawled || "Never"}\n`;
          output += `**Type:** ${result.type || "Unknown"}\n`;
        }
    
        return { content: [{ type: "text" as const, text: output }] };
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. Adds valuable return value information ('Shows when the URL was last submitted') but omits safety profile (read-only nature), rate limits, error handling for unsubmitted URLs, and required OAuth scopes despite having auth parameter.

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 sentences, zero waste. First sentence establishes purpose and API context; second sentence discloses return value. Perfectly front-loaded with no redundant or filler text.

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?

Appropriately complete for a 2-parameter tool with no output schema. Covers core functionality and return value. Minor gap: lacks explicit read-only safety declaration needed in absence of annotations, but sufficient for agent selection and invocation.

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 has 100% description coverage (url and access_token fully documented), establishing baseline 3. Description adds contextual framing ('via Google Indexing API') but does not expand on parameter semantics, formats, or constraints beyond what the schema already 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?

Excellent specificity with 'Check the indexing notification status' (verb + resource), explicitly references 'Google Indexing API' to distinguish from IndexNow siblings, and clearly differentiates from google_indexing_submit via the 'status' action vs submission.

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?

Implies usage pattern (checking status vs submitting) through the action verb and sibling name contrast, but lacks explicit when-to-use guidance, prerequisites, or explicit comparison stating 'use this after submitting to verify status.'

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