Skip to main content
Glama

Honeyfield Marketing MCP

Search Console: URL inspection

sc_url_inspection
Read-only

URL Inspection: Indexierungsstatus, Canonicals und Crawl-Signale für eine URL. Die URL muss innerhalb der konfigurierten Search-Console-Property liegen. Rückgabe: verdict, coverage_state, indexing_state, google_canonical, user_canonical, last_crawl, robots_txt_state (ALLOWED/DISALLOWED), page_fetch_state (SUCCESSFUL, SOFT_404, BLOCKED_ROBOTS_TXT, NOT_FOUND, ...). mobile_verdict und mobile_issues erscheinen nur, wenn Google den (eingestellten) Mobile-Usability-Teil noch mitliefert — fehlen sie, wurde nichts geprüft. Fehler kommen als Dict mit error (missing_permission/not_found/rate_limited/ auth_error/http_error), message und hint zurück. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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

Input Schema

NameRequiredDescriptionDefault
urlYes
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds meaningful behavioral context: conditional mobile fields only when Google supplies them, specific error categories such as missing_permission, rate_limited and auth_error, and the Search Console property boundary. There is no contradiction with the annotations.

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?

The purpose and key property constraint are front-loaded, and the text is generally efficient. The return-field list is lengthy and partly duplicates the existing output schema, but the conditional mobile note and error structure still earn their place.

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?

For a read-only inspection tool that already has an output schema and read-only/open-world annotations, the description supplies the remaining operational context: property scope, optional workspace behavior, conditional mobile fields and error modes. Nothing essential for correct invocation appears to be missing.

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?

Schema description coverage is 0%, so the description must compensate; it does so by explaining that url must belong to the configured Search Console property and that workspace is an optional customer-workspace slug. It could be slightly stronger by specifying the expected URL format (for example scheme/host), but both parameters receive useful meaning beyond the bare schema.

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 opening sentence names a specific operation (URL Inspection) and enumerates the exact facets: indexing status, canonicals and crawl signals for a single URL. This is much more specific than a generic Search Console query and distinguishes it from sibling performance, sitemap and site-management tools.

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?

It states the key prerequisite that the URL must reside within the configured Search Console property, and explains that workspace is optional when only one workspace exists. It does not explicitly contrast this tool with alternatives such as bing_url_info or site_crawler_check, so it falls short of 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.

Resources