Skip to main content
Glama

List connected Search Console properties

edgeo_search_console_sites
Read-only

List Google Search Console properties for your locally authorized Google account, optionally filtering property URLs by a case-insensitive substring. Requires prior search-console connection setup.

Instructions

List Google Search Console properties for the user's locally authorized Google account. Requires prior setup with edgeo-mcp search-console connect; uses a read-only OAuth scope and returns only properties the Google account can access. Optionally filter property URLs by a case-insensitive substring.

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

Input Schema

NameRequiredDescriptionDefault
siteUrlContainsNoOptional case-insensitive substring to filter property URLs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / siteUrlContains
      Added value: +{
      +  "description": "Optional case-insensitive substring to filter property URLs.",
      +  "maxLength": 2048,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: it discloses the read-only OAuth scope, the setup prerequisite, and that results are limited to properties the account can access. Annotations already cover safety (readOnlyHint), so this is meaningful supplementary disclosure. It stops short of describing empty-result or pagination behavior.

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-loads the action and resource, then layers prerequisite, scope, and filtering in a compact sequence. Every clause carries information an agent would otherwise have to guess.

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?

For a single-optional-parameter read tool with annotations covering safety and no output schema, the description covers prerequisites, authorization scope, and filtering. Only the return shape (list of property URLs plus any metadata) is left implicit, a minor gap.

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?

With one parameter at 100% schema coverage, the schema already documents siteUrlContains including its case-insensitive substring semantics. The description restates that fact without adding syntax, matching, or edge-case guidance, so this is the baseline 3.

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 (List) and resource (Google Search Console properties) with scope qualifiers ('for the user's locally authorized Google account'). An agent can distinguish this discovery tool from siblings like edgeo_search_console_query or edgeo_import_search_console_csv 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 Guidelines4/5

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

Explicitly names the prerequisite ('Requires prior setup with `edgeo-mcp search-console connect`'), which is the main usage gate an agent needs to check. It does not explicitly route to alternatives (e.g. that results feed siteUrl into edgeo_search_console_query), so it stops short of a 5.

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