Skip to main content
Glama
ahonn

Google Search Console MCP Server

by ahonn

list_sites

Retrieve all websites and properties registered in your Google Search Console account to manage and analyze search performance data.

Instructions

List all sites in Google Search Console

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the list_sites tool. Calls Google Webmasters API's sites.list() method via authenticated client to retrieve list of verified sites.
    async listSites() {
      const webmasters = await this.getWebmasters();
      return webmasters.sites.list();
    }
  • src/index.ts:44-47 (registration)
    Registration of the list_sites tool in the MCP list_tools response handler, including name, description, and JSON schema for empty input (no parameters).
      name: 'list_sites',
      description: 'List all sites in Google Search Console',
      inputSchema: zodToJsonSchema(z.object({})),
    },
  • MCP call_tool dispatch case for list_sites that instantiates the SearchConsoleService, calls its listSites method, and returns the response as formatted text content.
    case 'list_sites': {
      const response = await searchConsole.listSites();
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Input schema definition for list_sites tool: empty object schema indicating no input parameters are required.
    inputSchema: zodToJsonSchema(z.object({})),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List all sites' implies a read-only operation, it doesn't specify authentication requirements, rate limits, pagination behavior, or what 'all sites' means in practice (e.g., all sites the authenticated user has access to).

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, efficient sentence that communicates the essential purpose without any wasted words. It's appropriately sized for a simple list operation and front-loads the key information.

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 zero-parameter list operation with no output schema, the description is minimally adequate. However, without annotations and with multiple sibling tools, it should ideally provide more context about when this tool is appropriate versus alternatives and what the output format looks like.

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 tool has zero parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and the schema already fully documents this.

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 clearly states the verb ('List') and resource ('sites in Google Search Console'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_sitemaps' or 'get_sitemap', which would require more specific scope definition.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'list_sitemaps' and 'get_sitemap' available, there's no indication of when a user would need to list sites versus sitemaps, or whether this should be used before other operations.

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/ahonn/mcp-server-gsc'

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