Skip to main content
Glama
Sign In

Squish

by co.squish
OverviewDiscussionsAdmin

Remove ai visibility coverage

remove_ai_visibility_coverage
Destructive

Removes a domain from a customer's AI Visibility coverage, freeing its slot. The plan's own site can never be removed. Its scan history for that domain is dropped. Two-step: confirm:false previews, confirm:true removes ONLY after an explicit yes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>",
      "coveredDomain": "<coveredDomain>"
    },
    "name": "remove_ai_visibility_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe hosting plan's domain.
confirmNofalse (default) previews; true removes it. Pass true ONLY after explicit user confirmation.
coveredDomainYesThe covered domain to remove.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/readOnlyHint annotations by disclosing concrete consequences: the slot is freed, the plan's own site is a permanent exclusion, and the domain's scan history is dropped. It also surfaces the confirm-gated two-phase behavior, which is the key operational trait for an irreversible mutation.

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?

Four short sentences, each carrying a distinct fact: what is removed, the hard exclusion, the data loss, and the confirmation protocol. The irreversible constraint and confirmation gate are front-loaded where an agent will see them.

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 destructive, non-idempotent mutation with no output schema, the description covers consequences, constraints, and the safe invocation protocol. The only gap is what the confirm:false preview actually returns, which an agent may want to know before calling.

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 domain and coveredDomain are already fully documented and the description rightly does not re-explain them. The description reinforces the confirm gating semantics ('ONLY after an explicit yes') at a policy level, which adds a little meaning beyond the per-field text.

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?

Specific verb (removes) plus resource (a domain from a customer's AI Visibility coverage) with the side effect named (freeing its slot). It is immediately distinguishable from the sibling add_ai_visibility_coverage without inspecting either 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?

Gives a clear precondition (the plan's own site can never be removed) and an explicit two-step protocol: confirm:false to preview, confirm:true only after an explicit user yes. It does not point to get_my_ai_visibility_coverage as a way to check current coverage first, so the alternative-routing guidance is slightly incomplete.

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

All Squish toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources