Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

List Search Console sites

seo_list_search_console_sites
Read-onlyIdempotent

Lists the Search Console properties visible to each Google account the calling user has connected in the Sextant dashboard, and flags the one bound to the project. Use it to find the siteUrl (e.g. sc-domain:example.com or https://www.example.com/) and accountId to pass to seo.set_search_console_site. Cannot connect a new Google account; that happens on the project's Integrations page. Uses no credits. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "seo_list_search_console_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/destructive/closed-world, so the description's job is to add context — and it does: it discloses credit cost ('Uses no credits'), the cross-account listing scope, that the project-bound property is flagged, and the account-connection limitation. It stops short of describing empty-result or pagination behavior when the user has no connected accounts, keeping it from a 5.

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?

Front-loaded with what it lists before moving to the downstream use, the boundary, and the cost. Every sentence earns its place; nothing is redundant with the title or annotations.

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?

With no output schema, the description carries the return-value burden and does so at the right level: it names the key fields (siteUrl with concrete formats 'sc-domain:example.com' or 'https://www.example.com/', accountId) and the project-binding flag. Only edge-case behavior (no connected accounts, multiple accounts) is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter (siteId), so the baseline is 3. The description never mentions siteId or how it scopes the account/property listing, adding no meaning beyond the schema.

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?

States a specific verb and resource ('Lists the Search Console properties') plus scope ('visible to each Google account the calling user has connected') and a distinguishing behavior ('flags the one bound to the project'). An agent can distinguish this from sibling listers like list_sites or seo_get_search_console_performance without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names the downstream action the output enables ('Use it to find the siteUrl ... and accountId to pass to seo.set_search_console_site') and draws a hard boundary on what this tool cannot do ('Cannot connect a new Google account; that happens on the project's Integrations page'). When-to-use, when-not, and where else to go are all present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources