Skip to main content
Glama

launchfiles_seo_indexing_status

Read-onlyIdempotent

Inspect live Google Search Console sitemap and per-URL indexing status for a domain or URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "launchfiles_seo_indexing_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https:// URL to inspect in Google Search Console.
inspectUrlsNoCheck individual sitemap URLs via Google URL Inspection API (default true).
maxInspectUrlsNoMax sitemap URLs to inspect per call (default 35, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / inspectUrls
      Added value: +{
      +  "description": "Check individual sitemap URLs via Google URL Inspection API (default true).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / maxInspectUrls
      Added value: +{
      +  "description": "Max sitemap URLs to inspect per call (default 35, max 50).",
      +  "type": "number"
      +}
  2. Added

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, and openWorldHint already implies external calls, so "live Google Search Console" adds little. With annotations carrying the safety profile, the description's remaining burden was to disclose GSC authentication/connection requirements, API quota or rate-limit constraints (material here, since URL Inspection is quota-capped), and failure behavior when no GSC property matches — none of which appear.

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?

A single front-loaded sentence with zero filler, which is well proportioned for a three-parameter read tool. It is efficient but borders on terse given the complexity of the external dependency.

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?

With no output schema, the description carries some burden for describing what is returned (sitemap-level vs per-URL results, how many URLs are reported), and it says nothing about that or about the GSC connection prerequisite. The parameter-level detail is fully handled by the schema, so the gap is mainly around results and preconditions.

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 100%: url, inspectUrls, and maxInspectUrls (including the default 35 / max 50 behavior) are fully documented in the schema. The description adds no semantics about which parameter selection to prefer, 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?

"Inspect live Google Search Console sitemap and per-URL indexing status" gives a specific verb (inspect) plus two concrete resources (sitemap status, per-URL indexing status), and scopes it by input (domain or URL). It is clearly distinct from audit/drift-check siblings, though it never names an alternative explicitly.

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 phrase "live ... status" implies this is the tool for checking current indexing state, but there is no explicit when-to-use, no prerequisite (e.g. GSC must be connected), and no stated boundary against the audit or drift-check siblings. Usage has to be inferred from the resource name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.