Skip to main content
Glama

search_console_url_inspection_inspect

Inspect a URL's indexing state using Search Console's URL Inspection API to diagnose why a page isn't ranking. Returns verdict, coverage state, crawl time, and mobile usability.

Instructions

Inspect a single URL's indexing state via the Search Console URL Inspection API. Returns the raw inspectionResult envelope: {inspectionResult:{inspectionResultLink (live UI URL), indexStatusResult:{verdict ('PASS'|'PARTIAL'|'FAIL'|'NEUTRAL'), coverageState (string, e.g. 'Submitted and indexed' / 'Crawled - currently not indexed' / 'Discovered - currently not indexed'), robotsTxtState, indexingState, lastCrawlTime (ISO 8601), pageFetchState, googleCanonical, userCanonical, referringUrls, sitemap}, mobileUsabilityResult, richResultsResult?, ampResult?}}. Read-only; no re-indexing is triggered. Rate limit: Search Console caps inspection at ~2000 URLs per property per day. Use this to debug why a specific page isn't ranking. For site-wide coverage numbers use search_console_sitemaps_list; for organic-performance metrics use search_console_analytics_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_urlYesProperty identifier as registered in Search Console. For URL-prefix properties use the full URL including trailing slash (e.g. 'https://example.com/'). For Domain properties use the 'sc-domain:' prefix (e.g. 'sc-domain:example.com'). The property must be verified and accessible to the authenticated Google account.
inspection_urlYesAbsolute URL to inspect (e.g. 'https://example.com/about'). Must be under site_url's property; cross-property inspection is rejected by the API.
Behavior5/5

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

Despite no annotations, description fully discloses read-only nature, rate limit of ~2000 URLs/day, and detailed return envelope structure including possible verdict values.

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?

Description is dense but front-loaded with purpose, then details, then constraints, then alternatives. Every sentence adds value; no redundancy.

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

Completeness5/5

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

No output schema, but description fully explains return structure including nested fields and values. Covers rate limits, read-only, and distinguishes from siblings. Complete for a complex tool.

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 coverage is 100%, so baseline is 3. Description adds minimal extra beyond schema (e.g., cross-property rejection note) but does not substantially enhance parameter meaning.

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?

Clear verb 'inspect', specific resource 'URL's indexing state', and explicit API source. Distinguishes from siblings by stating when to use other tools for site-wide coverage or performance metrics.

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

Usage Guidelines5/5

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

Explicitly states use case: 'debug why a specific page isn't ranking.' Provides alternatives: 'For site-wide coverage numbers use search_console_sitemaps_list; for organic-performance metrics use search_console_analytics_query.'

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/logly/mureo'

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