Skip to main content
Glama
acamolese

Google Search Console Audit MCP

gsc_sites

Retrieve a list of all verified sites in your Google Search Console account to identify which properties are accessible for auditing.

Instructions

List all verified sites in Google Search Console.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The gsc_sites function is a tool handler decorated with @mcp.tool(). It calls the Google Search Console API's /sites endpoint, iterates over siteEntry to extract siteUrl and permissionLevel for each verified site, and returns the results as a JSON string.
    @mcp.tool()
    def gsc_sites() -> str:
        """List all verified sites in Google Search Console."""
        data = _api_get(f"{BASE}/sites")
        results = []
        for site in data.get("siteEntry", []):
            results.append({"url": site["siteUrl"], "permission": site["permissionLevel"]})
        return json.dumps(results, indent=2, ensure_ascii=False)
  • The tool is registered via the @mcp.tool() decorator on the gsc_sites function. The mcp object is an instance of FastMCP (from mcp.server.fastmcp), and the decorator exposes the function as an MCP tool.
    @mcp.tool()
    def gsc_sites() -> str:
  • The _api_get helper is used by gsc_sites to make authenticated GET requests to the Google Search Console API. It adds an Authorization header with a Bearer token obtained via _get_token().
    def _api_get(url: str) -> dict:
        req = urllib.request.Request(url, headers={"Authorization": f"Bearer {_get_token()}"})
        with urllib.request.urlopen(req) as resp:
            return json.loads(resp.read())
  • The schema for gsc_sites: no input parameters (returns str). The function has no arguments, so the tool takes no user input. The return type annotation is str (a JSON string).
    @mcp.tool()
    def gsc_sites() -> str:
        """List all verified sites in Google Search Console."""
        data = _api_get(f"{BASE}/sites")
        results = []
        for site in data.get("siteEntry", []):
            results.append({"url": site["siteUrl"], "permission": site["permissionLevel"]})
        return json.dumps(results, indent=2, ensure_ascii=False)
Behavior2/5

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

With no annotations provided, the description fails to disclose behavioral traits like authentication requirements, potential errors, or limitations. The term 'verified' could use more context.

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?

The description is a single, front-loaded sentence with no wasted words. Every part earns its place.

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 simple list tool with an output schema, the description is mostly adequate. It could briefly mention the return type (e.g., list of site URLs), but the low complexity justifies a score of 4.

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 no parameters, and the description correctly reflects this. For a tool with 0 parameters, the baseline score is 4, and the description adds no unnecessary parameter info.

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 'List' and the resource 'all verified sites in Google Search Console.' It effectively distinguishes itself from siblings like gsc_site_details, which focuses on a single site.

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 description implies usage when needing a list of verified sites but provides no explicit guidance on when to use versus alternatives, such as gsc_site_details for individual site details.

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/acamolese/google-search-console-mcp'

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