Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

searchconsole.sites.delete

Remove a site property from the user's Search Console account permanently. Use it to clean up properties you no longer manage; the deletion is irreversible and blocked under read-only profiles.

Instructions

Removes a site from the set of the user's Search Console sites [HTTP DELETE] — removes the resource; irreversible unless the API documents a trash/undo flow; refused under --readonly safety profiles. Returns the post-delete resource state (or empty) as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: add, get, list.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
siteUrlYes[URL path segment] The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / siteUrl / description
      Previous value: -"The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`."New value: +"[URL path segment] The URI of the property as defined in Search Console. **Examples:** `http://www.example.com/` or `sc-domain:example.com`."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the burden well: it discloses irreversibility ("irreversible unless the API documents a trash/undo flow"), the --readonly safety-profile refusal, and the return shape (post-delete resource state or empty JSON). It omits permission/ownership requirements specific to Search Console property deletion.

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

Conciseness3/5

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

The core action and its danger are front-loaded, which is good. But the trailing explanation of building request bodies from typed parameters or `body_file` is generic boilerplate that is irrelevant to a bodyless DELETE and dilutes an otherwise tight sentence.

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?

For a mutation tool with no annotations and no output schema, the description covers the essential risks (irreversibility, readonly refusal) and the return value. What remains missing is limited to auth/ownership prerequisites.

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 coverage is 100%, so siteUrl, query, params, dry_run and body_file are already documented. The description's remark that typed flags win over the `params` map and that a body can come from `body_file` largely restates the schema's own parameter descriptions, adding no DELETE-specific guidance (e.g. siteUrl format variants).

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+resource ("Removes a site from the set of the user's Search Console sites") and explicitly distinguishes itself from siblings over the same resource (add, get, list). An agent can identify the operation without opening the schema.

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?

Names the sibling operations over the same resource (add, get, list), which gives clear routing context, and flags that the call is refused under --readonly safety profiles. It stops short of an explicit when/when-not rule (e.g. use add to re-register, use list to verify before deleting).

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