Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_url_inspection

Inspect one URL in Google Search Console to check indexing status, coverage, canonical, crawl time, robots and sitemaps; returns cached or refreshed results within quota.

Instructions

Live Google URL Inspection for one page: coverage_state, verdict (PASS / NEUTRAL / FAIL), indexing_allowed, Google vs user canonical, last_crawl_time, robots_txt_state, page_fetch_state, sitemaps, a referring-URLs sample, rich_results and mobile_usability. Cache-first — returns a fresh cached result or refreshes live from GSC within the property's inspection quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_url_inspection"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the cache-first strategy, that a live refresh is bounded by the property's inspection quota, and that a referring-URLs sample (not a full list) is returned. It stops short of stating auth/permission requirements or what happens when the quota is exhausted.

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?

Two sentences, front-loaded with purpose and returning-field inventory, then the operational caveat about caching and quota. The field list is dense but earns its place because no output schema is defined; only the long comma-separated enumeration hurts scannability slightly.

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?

No annotations and no output schema mean the description must cover behavior, and it largely does (caching, quota, partial sitemaps/referrer data). However, it never explains how the inspected page is identified given the tool takes no arguments, and it says nothing about failure modes such as quota exhaustion or properties without GSC access — significant gaps for a live-quota-bound call.

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

Parameters4/5

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

The tool exposes zero parameters, so there is no parameter semantics for the description to explain — the baseline for a 0-param schema applies. The phrase "for one page" implies a target page but no input field exists to supply it, which is a completeness concern rather than a parameter-documentation gap.

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 opens with a specific verb+resource, "Live Google URL Inspection for one page", and enumerates the concrete signals returned (coverage_state, verdict, canonical, last_crawl_time, robots_txt_state, rich_results, mobile_usability). That is enough to separate it from history/summary siblings like get_indexation_history, but it never names an alternative explicitly, so sibling differentiation is inferred rather than stated.

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?

Usage context is only implied: "Cache-first — returns a fresh cached result or refreshes live from GSC" hints at a freshness trade-off, but there is no statement of when to prefer this over get_page_detail, get_site_audit_page, or the indexation summary tools, and no when-not guidance.

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

Deploy Server

Other Tools