Skip to main content
Glama
mcp-google-gsc

mcp-google-gsc

by mharnett

gsc_list_sites

Lists all verified sites and properties in Google Search Console, helping you identify which properties are available for search analytics queries.

Instructions

List all verified sites/properties in Google Search Console.

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 observedv1.2.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does convey one meaningful restriction beyond the name: only *verified* sites for the authenticated user are returned, implying an auth requirement and a filtered result set. It says nothing about the shape of each site entry, permissions per site, or pagination/result limits, which are the remaining behavioral gaps.

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?

A single front-loaded sentence with no filler, hedging, or repetition. Nothing is wasted and the key qualifier ('verified') appears immediately.

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 tool is simple (no params, no nested objects) but has no output schema, so the description is the only place an agent could learn what a returned 'site' looks like (e.g., siteUrl and permission level). It also omits whether results are paginated. Adequate for invocation, but incomplete for interpreting the response.

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 takes zero parameters, so the input schema is empty and there is nothing for the description to clarify. Baseline for a no-parameter tool applies.

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 gives a specific verb plus resource ('List all verified sites/properties') and names the system (Google Search Console), so an agent knows exactly what it retrieves. It does not distinguish itself from the sibling tools (inspection, search_analytics, client_context), so it stops 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 Guidelines3/5

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

For a zero-parameter listing tool, the use case is strongly implied: call it to discover which properties the authenticated account can access before running inspection or analytics. However, the description never states this prerequisite relationship explicitly nor rules out any alternative, leaving the routing logic to inference.

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