Skip to main content
Glama

URL inspection results

list_url_inspections
Read-onlyIdempotent

Latest stored URL Inspection result per URL of the property: verdict, coverageState, indexingState, robotsState, pageFetchState, Google vs user canonical, lastCrawlTime, crawledAs, mobileVerdict, checkedAt, whether the URL is on the tracked list and lastSubmittedAt (last indexing request made with request_indexing, null if none). Filter by status (indexed / not_indexed) or by URL text. hasData=false when no inspection is stored yet. Use after get_indexing_tracker to see specific URLs, or to check one URL's state. / Resultado da inspeção de cada URL (indexada?, canonical, último crawl).

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": {
      "site": "<site>"
    },
    "name": "list_url_inspections"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesProperty: displayName ("example.com"), Search Console siteUrl ("sc-domain:example.com", "https://www.example.com/") or numeric id. A unique substring among visible properties also works ("exam"). list_sites shows the options. The value "demo" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; "demo" é um site de demonstração com dados fictícios, sem login e só leitura.
limitNoRows (default 100).
statusNoFilter (default all).
urlContainsNoOnly URLs containing this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. / Propriedade por nome, siteUrl ou id."New value: +"Property: displayName (\"example.com\"), Search Console siteUrl (\"sc-domain:example.com\", \"https://www.example.com/\") or numeric id. A unique substring among visible properties also works (\"exam\"). list_sites shows the options. The value \"demo\" selects a demonstration site with fictional data: it works without signing in and is read-only. / Propriedade por nome, siteUrl ou id; \"demo\" é um site de demonstração com dados fictícios, sem login e só leitura."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: only the LATEST stored snapshot is returned, hasData=false signals no inspection exists yet, and lastSubmittedAt is null when no request_indexing was ever made. The one gap is staleness — 'stored' implies the data may lag live Search Console, but it never says how fresh it is or whether results are cached.

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?

Front-loaded with the core statement, then usage routing, then the field inventory, which is warranted because there is no output schema. The only waste is the trailing Portuguese restatement duplicating the English purpose sentence, which lengthens the definition without adding information for an English-reading 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?

With no output schema, the description carries the return-value burden and does so by naming every field the agent will see, plus the hasData/null sentinels. Combined with annotations covering the safety profile, an agent has enough to call this correctly; only freshness/latency and result-size behavior (limit 2000, default 100) remain unexplained.

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%, so parameters are already documented, and the description mostly restates them ('Filter by status (indexed / not_indexed) or by URL text'). It adds the useful note that lastSubmittedAt records the last indexing request made with request_indexing, but that is about output semantics rather than parameter meaning. Baseline 3 applies since the schema does the heavy lifting.

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 opens with a precise verb+resource+scope: 'Latest stored URL Inspection result per URL of the property', then enumerates the shape of a record (verdict, coverageState, indexingState, robotsState, pageFetchState, canonicals, lastCrawlTime, checkedAt, lastSubmittedAt). This is materially different from the sibling get_indexing_tracker (tracked list) and the agent can distinguish them without opening a schema.

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

Usage Guidelines4/5

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

Explicit routing is given: 'Use after get_indexing_tracker to see specific URLs, or to check one URL's state', plus the two filtering modes. It stops short of stating when NOT to use it (e.g. when no inspection has ever been run, or for bulk history across crawls), so it is clear context rather than full when/when-not guidance.

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.