serve

Release link

release_link

Destructive

Release an owned link to free up its resource. Fails for remote links with published artifacts; unpublish them first, then release.

Instructions

Release (free) an owned link by label. Fails with remote_link while the label still has a published artifact; unpublish it with stop_remote first. Returns confirmation and the account's usage.

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": {
      "label": "<label>"
    },
    "name": "release_link"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes	Label of the link to release.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.8.6Sep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations declaring destructive behavior, the description discloses the failure mode (remote_link), a prerequisite (unpublish with stop_remote), and the expected return ('confirmation and the account's usage'). This gives the agent concrete behavioral expectations without an output schema.

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?

Three tightly packed sentences with no filler. The core action is front-loaded, followed by the key error condition and the return value; every sentence earns its place.

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 tool with no output schema, this description is complete: it specifies what to do, what can go wrong, how to recover, and what the response will contain. Nothing essential is missing for correct invocation.

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?

With schema description coverage at 100% and only one parameter, the schema already fully documents label. The description reinforces that the operation is by label but adds no additional parameter-specific meaning, so the baseline of 3 is appropriate.

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 description uses a specific verb ('Release (free)') with a clear resource ('an owned link by label') and distinguishes this operation from related link-management siblings by explaining the owned/remote distinction and the stop_remote prerequisite. This is enough for an agent to know what operation it is invoking.

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?

It gives a clear conditional workflow: if releasing fails with remote_link while a published artifact exists, use stop_remote first. This is explicit context for when this tool is appropriate, though it does not name a direct alternative for permanent revocation such as revoke_link.

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

Deploy Server