Snip

Delete a link

delete_link

DestructiveIdempotent

Permanently deletes one of the user's Snip.link links and its click history; its current and previous short URLs stop working within a minute and its current and previous endings remain reserved indefinitely, including for the same account. There is no automatic release, restore or reuse operation. Needs the user signed in to Snip.link. Confirm with the user first; to pause every ending instead, use update_link with disabled true.

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": {
      "link": "<link>"
    },
    "name": "delete_link"
  }
}

Input Schema

Name	Required	Description	Default
`link`	Yes	The full short URL (https://go.snip.link/abc123 or https://snip.link/r/abc123), its ending (abc123) or its id. Full URLs are scoped to their host; they never select a same-ending link on another domain.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

changedInput schema / properties / link / description

Previous value: -"The short link (https://snip.link/abc123), its ending (abc123) or its id."New value: +"The full short URL (https://go.snip.link/abc123 or https://snip.link/r/abc123), its ending (abc123) or its id. Full URLs are scoped to their host; they never select a same-ending link on another domain."

changedInput schema / properties / link / maxLength
```
Previous value: -120New value: +2048
```

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint/idempotentHint), it discloses that click history is destroyed, that URLs stop working within a minute, that endings stay reserved indefinitely even for the same account, and that there is no restore or reuse path — exactly the irreversible consequences an agent needs before calling.

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

Conciseness4/5

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

Dense but front-loaded: deletion and permanence come first, consequences second, the confirmation/alternative guidance last. Each sentence carries distinct information, though it reads as one long block that could be split for scannability.

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 single-parameter destructive tool with no output schema, the description covers irreversibility, timing, auth requirement, and the safer alternative — nothing an agent needs to decide or invoke correctly is missing.

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% and the parameter's own description already explains the accepted URL/ending/id forms and host scoping, so the description adds no parameter-level meaning. Baseline 3 applies where the schema does all the work.

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 ("Permanently deletes one of the user's Snip.link links and its click history") and makes the scope explicit, so it is clearly distinguishable from update_link (pause) and drop_file (file deletion).

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

Usage Guidelines5/5

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

Gives an explicit precondition ("Confirm with the user first") and names the concrete alternative with its argument ("to pause every ending instead, use update_link with disabled true"), which routes the agent to the non-destructive sibling when appropriate.

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

All Snip tools Inspect

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

Need Help?