google-search-console-mcp

Overview Schema Source Related Servers Discussions Admin

Remove a property

delete_site

DestructiveIdempotent

Remove a property from Google Search Console. First call returns a confirmation token, then call again with the token to confirm deletion.

Instructions

Removes a property from Search Console. Two-step: the first call returns a confirmation token, the second performs the removal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site_url`	Yes	The Search Console property: "sc-domain:example.com" for a domain property, or "https://example.com/" for a URL-prefix property (the trailing slash is required)
`confirm_token`	No	The token from this tool's previous refusal. Call without it first to see what would happen and receive the token; it cannot be guessed or reused.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`site`	Yes
`removed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.0Sep 8, 2026
- addedInput schema / properties / confirm_token / maxLength
```
Added value: +64
```
- addedInput schema / properties / site_url / maxLength
```
Added value: +2048
```
First observedv0.2.0Sep 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The description explicitly states the destructive action (removes a property) and the confirmation-token mechanism, which safely discloses the multi-step removal process. The annotations already indicate destructive and idempotent, and the description adds useful procedural detail without contradiction.

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?

The description is two clear sentences with no unnecessary details. It efficiently conveys the core purpose and the two-step process, making it easy for the agent to understand the tool's behavior.

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?

The description is sufficient for an agent to invoke the tool correctly: it states that the first call returns a token and the second performs the removal. It does not cover edge cases like non-existent properties, but the output schema is available and the annotations cover safety aspects, so overall context is adequate.

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?

The schema descriptions for both parameters are complete and already explain the confirmation-token flow. The tool description echoes this but does not add significant additional meaning beyond what the schema provides, so it meets the baseline for 100% schema coverage.

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?

The tool name, title, and description all clearly state that this tool removes a property from Search Console. The distinction from sibling tools like unverify_site and add_site is implicit, and the two-step nature is described.

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

Usage Guidelines3/5

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

The description explains the two-step workflow (first call returns a token, second call performs the removal), which is a key usage guideline. However, it does not explicitly compare with sibling tools or mention prerequites like ownership verification, so some context is missing.

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