Skip to main content
Glama
amirjahfar1

Google Search Console (GSC) MCP

by amirjahfar1

check_indexing_issues

Check a list of URLs for indexing problems such as crawl errors or exclusion. Diagnose and resolve issues to improve Google search visibility.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYes
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as rate limits, read-only vs mutation, error handling, or response format. The description carries full burden but gives minimal behavioral context.

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 relatively concise and structured with clear bullet points for parameters. However, the 'Args:' section could be integrated more seamlessly for brevity.

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?

Having an output schema reduces the need to describe return values, but the description lacks details on error behavior, maximum URLs, and prerequisites. It 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?

Schema coverage is 0%, but the description adds meaning: explains site_url format with examples and specifies that urls should be 'one per line'. This adds value beyond the plain schema types.

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 clearly states the verb 'check' and the resource 'indexing issues' across multiple URLs. It distinguishes from sibling tools like inspect_url_enhanced (single URL inspection) by specifying multiple URLs.

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?

Provides explicit guidance on site_url format (e.g., domain vs site-level property) and how to filter by page. However, lacks explicit instructions on when not to use this tool compared to alternatives like batch_url_inspection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/amirjahfar1/Google-Search-Console-GSC-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server