Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

search_console_inspect_url

Inspect a URL's indexed status in Google Search Console to confirm indexation and troubleshoot visibility.

Instructions

Read Google's indexed status for one URL under a Search Console property.

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": {
      "inspection_url": "<inspection_url>"
    },
    "name": "search_console_inspect_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlNoSearch Console property, for example sc-domain:example.com. Use list_sites to find one.
language_codeNoen-US
inspection_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load; it does disclose that this is a read operation of Google's index status. It says nothing about authentication, per-property quota consumption, behavior for URLs not in the property or not indexed, or latency.

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 front-loaded sentence that identifies the verb, the resource, and the scope with no filler. Nothing could be removed without losing meaning.

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?

For a three-parameter read tool with no output schema and no annotations, the description covers purpose adequately but omits what the response contains, failure modes, and the language_code semantics. It is minimally sufficient rather than complete.

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 only 33%, so the description needs to compensate: it usefully separates the single URL from the owning property, which maps to inspection_url and site_url. The language_code parameter and the URI format constraint are left entirely to the schema.

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 gives a specific verb ('Read') and resource ('indexed status for one URL under a Search Console property'), which an agent can distinguish from the list/report siblings. It stops short of explicitly naming an alternative, but the intent is unambiguous.

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?

The phrase 'for one URL under a Search Console property' implies the appropriate usage context (single-URL checking within a known property), but there is no statement of when not to use it, no prerequisites, and no referenced alternatives despite many sibling tools.

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