Skip to main content
Glama
thenavidm

Google Search Console MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove a property

delete_site
Destructive

Remove a Google Search Console property from an account. Set confirm to true to proceed; re-adding and re-verifying is required to restore access.

Instructions

Remove a property from this Google account's Search Console. The site's history is no longer readable by this account until the property is re-added and re-verified, and Google does not offer an undo. Set confirm to true to proceed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesThe Search Console property. Either a URL-prefix property ("https://navid.me/", trailing slash included) or a domain property ("sc-domain:navid.me"). A bare hostname is read as a domain property. Call list_sites for the exact strings this account owns, because the two shapes are different properties and mixing them up returns a 403.
accountNoWhich signed-in Google account to act as, by email. Omit to use the default. Call list_accounts to see what is signed in.
confirmNoSet true only when the user asked for exactly this action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / confirm / default
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Removing a property cuts this account off from its search history until it is re-added and re-verified. Set true to proceed."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover destructiveHint=true and idempotentHint=false, yet the description adds critical non-redundant behavior: history is no longer readable until re-added and re-verified, and Google offers no undo. This is exactly the extra context an agent needs before firing a destructive call.

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?

Two sentences, zero waste: the first states what and where, the second front-loads the irreversibility before the confirm instruction. Nothing repetitious.

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 destructive, non-idempotent mutation with no output schema, the description supplies the consequence and undo profile, and annotations cover the safety flags. An agent has everything needed to decide and call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds the meaning of the confirm gate ("Set confirm to true to proceed"), clarifying it as an active authorization step rather than merely an optional flag. The site/account parameter semantics come entirely from the schema.

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 ("Remove a property from this Google account's Search Console") with scope qualifier. It is clearly distinguishable from siblings like delete_sitemap or verify_site, which operate on different sub-resources.

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 clear context for when to invoke — it warns that history becomes unreadable and there is no undo, then instructs "Set confirm to true to proceed." It does not explicitly name an alternative tool or a when-not condition, but the destructive consequence framing provides adequate invocation context.

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

Deploy Server

Other Tools