Skip to main content
Glama
@mgcrea/mcp-google-search-console

@mgcrea/mcp-google-search-console

by mgcrea

Search Console: List Sites

gsc_list_sites
Read-only

Lists Google Search Console properties accessible to the signed-in account, with exact site URLs and permissions to use as the site parameter in other tools.

Instructions

The Search Console properties the signed-in account can see, each with its exact site_url (pass it as site to the other tools), kind and permission_level. A domain property (sc-domain:example.com) covers every protocol and subdomain; a URL-prefix property (https://www.example.com/) covers exactly that scheme, host and path, so http, https and www are separate properties with separate data. siteUnverifiedUser means listed but unreadable. Always fetches fresh; costs one request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gsc_list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description adds that it always fetches fresh data, costs one request, and explains that `siteUnverifiedUser` means listed but unreadable. It also discloses the important behavioral distinction between domain properties and URL-prefix properties, which affects how data is scoped.

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 compact and front-loaded: the first sentence states what is returned and the key field, followed by necessary property semantics, unverified status, and cost. Every sentence contributes useful information without repeating annotation details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately explains the return fields and property-type semantics. It also covers behavioral details such as freshness, request cost, and unreadable properties, which is sufficient for an agent to call this zero-parameter discovery tool correctly.

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?

There are no input parameters, so the baseline is 4. The description adds useful cross-tool context by saying the returned `site_url` should be passed as `site` to other tools, but this is not input parameter documentation and no additional parameter semantics are needed.

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 precisely identifies the resource: Search Console properties visible to the signed-in account, including the key `site_url`, `kind`, and `permission_level` fields. It distinguishes this discovery/list purpose from sibling tools by explaining that the returned `site_url` is passed as `site` to the other tools.

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?

The description gives clear implied usage guidance: use this to discover visible properties and obtain the `site_url` needed by other tools. It also notes the request cost and freshness, but it does not explicitly state when not to use it or name a direct alternative.

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