GSC MCP Server

check_indexing_issues

Detect indexing issues across multiple URLs using Google Search Console, showing specific problems for each URL.

Instructions

Check for specific indexing issues across multiple URLs.

Args: site_url: Exact GSC property URL from list_properties (e.g. "https://example.com/" or "sc-domain:example.com"). Domain properties cover all subdomains — use the domain property as site_url and filter by page to analyze a specific subdomain. urls: List of URLs to check, one per line

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>",
      "urls": "<urls>"
    },
    "name": "check_indexing_issues"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes
`site_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Check for specific indexing issues' and then describes arguments; it does not mention whether this is a read-only operation, any required permissions, rate limits, or what the check actually does (e.g., API calls). This lacks critical context for an AI agent to understand side effects.

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 description is compact and well-structured: a single-sentence purpose followed by an 'Args:' section. Every sentence adds value, with no redundant phrasing. The parameter explanations are pertinent and organized, though the purpose line could be slightly more specific.

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?

The description covers both parameters well and the output schema exists, so return values need not be explained. However, it omits behavioral context such as whether the tool is read-only, any constraints on the number of URLs, or the meaning of 'indexing issues.' For a simple check tool with two well-described parameters, this is adequate but not comprehensive.

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 input schema has 0% description coverage, so the description must compensate. It does so effectively: site_url is explained with exact format examples and domain-vs-prefix distinctions, and urls is defined as a list of URLs one per line. This adds meaning beyond the bare schema, though it could be more precise about URL formatting or limits.

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 states the tool's function clearly: 'Check for specific indexing issues across multiple URLs.' This has a specific verb ('Check'), a resource ('indexing issues'), and scope ('across multiple URLs'), distinguishing it from single-URL inspection tools. However, it doesn't explicitly name alternatives or enumerate what types of indexing issues are covered, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus sibling tools like inspect_url_enhanced or batch_url_inspection. It only provides parameter-level instructions (e.g., using the domain property for subdomain analysis), which does not clarify tool selection. No exclusions or alternative recommendations are given.

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