Skip to main content
Glama
modelbrain-search-console

modelbrain-search-console

Official

Inspect a URL

inspect_url
Read-onlyIdempotent

Check Google index status for a single URL in a Search Console property, including coverage state, last crawl time, chosen canonical, robots.txt state, and rich result checks.

Instructions

Google's index status for one URL in a property: whether it is indexed, coverage state, last crawl time, Google's chosen canonical, robots.txt state and rich result checks.

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_url": "<site_url>",
      "url": "<url>"
    },
    "name": "inspect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full URL to inspect. It must belong to site_url.
site_urlYesThe Search Console property, for example sc-domain:example.com or https://example.com/. A plain domain or page URL also works: it is matched to the right property.
language_codeNoLanguage for messages, for example en-US. Default: en-US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds real value by disclosing what is reported, but stays silent on operational behavior an agent would want: inspection quota/rate limits, what happens when the URL is unknown to the property, or whether results reflect cached data.

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?

A single sentence that leads with the verb-and-scope phrase before the field list, with no filler or redundant restatement of the title. The enumerated data points are dense but each one tells the agent something it would not otherwise know.

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?

For a read-only lookup with no output schema, the description carries the return-value burden well by naming the reported fields. It is near-complete but omits error/edge behavior (URL outside the property, unindexed URLs) and any quota context, which matter for an open-world API-backed inspection.

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 the schema already documents url, site_url and language_code including the property-matching rule and the default language. The description only restates the one-URL-one-property relationship, adding nothing about formats or defaults beyond the schema, which is the expected baseline for full coverage.

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 names a specific resource scope (index status for one URL within a property) and enumerates the exact data points returned: indexed state, coverage state, last crawl, chosen canonical, robots.txt state, rich results. That combination is unmistakably distinct from the sibling list/aggregate tools (list_sites, list_sitemaps, search_performance, compare_periods), so an agent can route without opening the schema.

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?

There is no explicit when-to-use or when-not-to-use statement and no named alternative, so guidance is only implied by the resource scope ('one URL'). An agent can infer this is the single-URL diagnostic versus the bulk/aggregate siblings, but it is inference rather than instruction.

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