list_sites_toolRetrieve all Search Console properties your authenticated account can access, including site URLs and permission levels. Use to manage or audit your site list.
List all Search Console properties accessible by the authenticated user.
Returns: List of site entries with permission levels and site URLs
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already declares this is a safe read. The description adds that access is scoped to the authenticated user and that results include permission levels, which is useful context. No pagination or rate-limit note, but with annotations covering safety a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the core action, plus a compact Returns block. No waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values needn't be explained, and the description still highlights the useful fields (permission levels, URLs). For a zero-param read tool this is nearly complete; only the sibling distinction is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the baseline is 4. Nothing to misdocument, and the description correctly implies no filtering inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('List all Search Console properties') scoped to the authenticated user. It is distinguishable from get_site_tool (singular) and add/delete_site_tool, but doesn't explicitly contrast with the closest sibling. Clear but no sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage (retrieve all properties) but no explicit when-to-use vs get_site_tool, no exclusions, no prerequisites. An agent can infer intent but must reason about alternatives itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.