Retrieve verified site properties from Google Search Console and Bing Webmaster Tools, including permission levels. Filter by search engine if needed.
List all verified sites (properties) across Google Search Console and Bing Webmaster Tools, along with permission levels.
| Name | Required | Description | Default |
|---|---|---|---|
| engine | No | Search engine to list properties for: 'google', 'bing', or 'all' (default: 'all') | all |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden. 'List' indicates a read-only, non-destructive operation, but the description does not mention authentication requirements, response format, pagination, or any side-effect guarantees. It is adequate for a simple list tool but not richly transparent.
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?
A single sentence that front-loads the core action and resource, then adds the permission-level output detail. Every word earns its place; no redundant filler or repetition of schema content.
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?
For a one-parameter, no-output-schema list tool, the description covers the essential purpose and result content. It does not describe the exact return structure or pagination, but the tool is simple enough that this omission is a minor gap rather than a blocker.
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?
The single parameter 'engine' is fully described in the schema with an enum and default, so schema coverage is 100%. The description adds no additional parameter-specific meaning beyond naming the two platforms, which the enum already conveys. Baseline 3 is appropriate.
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 ('List') and resource ('verified sites/properties') across two named platforms, and includes the permission-level detail. This clearly distinguishes it from sibling tools like list_sitemaps 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description conveys clear context: use this tool to get all verified sites across Google Search Console and Bing Webmaster Tools. It does not explicitly name alternatives or exclusion conditions, but the scope is unambiguous enough for an agent to select it appropriately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.