Skip to main content
Glama

search_console_url_inspection_inspect

Inspect a URL's indexing status to debug coverage issues, mobile usability, or rich results; returns detailed verdict and crawl data without triggering re-indexing.

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.
Behavior4/5

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

Without annotations, the description fully describes the output structure and declares it as read-only ('no re-indexing is triggered'). It also notes the daily rate limit. However, it does not mention error conditions or latency, which would enhance transparency further.

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?

The description is a single paragraph that efficiently conveys purpose, output structure, constraints, and usage guidance. It is front-loaded and every sentence adds value without unnecessary fluff.

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?

Given the complexity of the tool (nested output, no output schema), the description adequately compensates by detailing the result envelope, rate limits, and usage context. It covers all necessary aspects for an agent to use the tool correctly.

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%, and the description does not add additional parameter-level semantics beyond what's in the schema. The baseline score of 3 is appropriate as the description provides context but no new parameter details.

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 explicitly states 'Inspect a single URL's indexing state' and distinguishes from sibling tools like search_console_sitemaps_list and search_console_analytics_query. The verb 'inspect' and resource 'URL's indexing state' are clear and specific.

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?

The description provides explicit usage guidance: 'Use this to debug why a specific page isn't ranking' and directly names alternatives for site-wide coverage (search_console_sitemaps_list) and performance metrics (search_console_analytics_query). It also mentions the rate limit.

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