Skip to main content
Glama
modelbrain-search-console

modelbrain-search-console

Official

List Search Console properties

list_sites
Read-onlyIdempotent

Retrieve all Google Search Console properties available to the signed-in account with their permission levels. Use it first to get exact property names before running searches or inspections.

Instructions

List every Search Console property this Google account can see, with its permission level. Call this first to get exact property names.

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": "list_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real context beyond them: the result is scoped to what the authenticated account can access and each entry carries a permission level, which tells the agent what to expect from the response.

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?

Two short sentences with no waste, and the output content is front-loaded before the call-first advice.

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?

For a zero-parameter read-only listing tool with no output schema, the description covers scope, returned fields and sequencing — everything an agent needs before calling it.

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 schema is empty with zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly avoids inventing parameters and instead clarifies the implicit scope filter (the authenticated Google account).

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 (list) and resource (Search Console properties) plus scope (every property this Google account can see) and payload (permission level). It does not name a sibling or draw an explicit contrast, so it falls just short of the top band, but no agent could confuse this with list_sitemaps, search_performance, compare_periods or inspect_url.

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?

"Call this first to get exact property names" is an explicit sequencing instruction that tells the agent when to reach for this tool. There is no when-not guidance and no alternative is named, which keeps it out of the 5 band.

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