QuerySail: Google Search Console

List Search Console properties

list_properties

Read-onlyIdempotent

Use this when the user asks which Google Search Console sites or properties they can access, or to find the exact property_id for a site. Returns exact property IDs (Domain properties look like 'sc-domain:example.com', URL-prefix properties like 'https://example.com/'), the permission level, and connection status. The same site is listed once even if several connected Google accounts can see it. A site name can match more than one property, for example a Domain property and a URL-prefix property. Read-only. Does not change anything 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": "list_properties"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque cursor from a previous result's coverage.nextCursor.
`connection_id`	No	Optional: only list properties visible to this Google connection (connectionId from a previous result).

Output Schema

Name	Required	Description	Default
`notes`	No
`coverage`	No
`properties`	No
`connections`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026
- removedOutput schema / properties / requestId
```
Removed value: -{
-  "type": "string"
-}
```
First observedOct 6, 2026

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, and destructiveHint=false, so the safety profile is covered (and the 'Read-only' sentence partly repeats it). The description earns credit for disclosures the annotations cannot carry: deduplication across multiple connected accounts, the ambiguity of a site name matching both a Domain and a URL-prefix property, and the exact ID formats returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, then the return shape and the important edge cases (dedup, name ambiguity). Slightly padded by the closing 'Read-only. Does not change anything' pair, which restates the readOnlyHint annotation twice.

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 two-parameter read-only listing tool with a full output schema, the description covers everything an agent needs: when to call it, what identifiers come back and in what format, and the ambiguity case that could otherwise cause a wrong property selection. Return-value detail beyond this is delegated correctly to the output schema.

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%, so both cursor and connection_id are already documented in the schema, and the description adds no further meaning about them. Baseline 3 applies; the description's mention of connection status and permission level describes output, not the parameters.

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 ('which Google Search Console sites or properties they can access') plus a secondary purpose ('find the exact property_id for a site'). This clearly separates it from sibling tools like get_performance or inspect_urls, which operate on a property rather than enumerating them.

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?

Gives explicit triggering conditions: when the user asks which sites/properties they can access, or when a property_id is needed for another call. It does not name a when-not case or an alternative tool, but the usage context is unambiguous for a discovery tool.

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

All QuerySail: Google Search Console tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.