Skip to main content
Glama

Outil.io

Inspect URL index

inspect_url_index
Read-only

Inspection d’URL Search Console : la page est-elle indexée ? couverture, dernier passage de Googlebot, canonique choisie par Google vs déclarée, robots, ergonomie mobile, résultats enrichis détectés.

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": {
      "siteUrl": "<siteUrl>",
      "url": "<url>"
    },
    "name": "inspect_url_index"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
siteUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description does add real context beyond them: it discloses that data comes from Google Search Console (an external, live source) and lists the diagnostic dimensions returned. It stops short of noting that the siteUrl must be an owned/verified property or that results reflect Google's latest crawl state, which matter for interpreting output.

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?

One compact sentence, front-loaded with the tool's identity and resource, followed by a scannable list of what is checked. Every clause carries information, though the dense enumeration of facets is slightly compressed and lacks a lead-in on what is returned.

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 does a reasonable job of implying the returned diagnostics by listing them. However, for a two-parameter tool whose parameters are entirely undocumented in the schema, it leaves the siteUrl/url relationship and the auth/property-ownership requirement unexplained, which is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for the two required parameters. It never explains the crucial distinction between siteUrl (presumably the Search Console property) and url (the specific page to inspect), nor the required URI format. A caller could easily swap them.

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 pairs a specific verb ('Inspection d'URL Search Console') with a concrete resource and enumerates the facets examined: indexation status, coverage, last Googlebot crawl, Google-selected vs declared canonical, robots directives, mobile usability, and detected rich results. An agent can tell this is a per-URL Search Console index check. It does not, however, distinguish itself from plausible siblings such as audit_seo or inspect_page_region.

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?

There is no when-to-use / when-not-to-use guidance and no mention of alternatives for related questions (site-wide SEO auditing, page-region inspection). The phrase 'Search Console' implies the data source but not the conditions under which this tool is the right choice. Prerequisites such as needing a verified Search Console property are absent.

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.