Skip to main content
Glama

Disable link · 停用短链(短.在线)

disable_link
DestructiveIdempotent

停用你拥有的短链,停用后短链和二维码将停止跳转。需要 links:disable 与已验证邮箱。幂等。 Disable a link you own: its short link and QR code stop redirecting. Requires links:disable and a verified email. Idempotent.

Input Schema

NameRequiredDescriptionDefault
idYesShort code or link id for a link you own.

Output Schema

NameRequiredDescriptionDefault
idNo
okYes
codeNo
toolNo
typeNo
errorNo
stateNo
titleNo
featureNo
messageNo
retryableNo
short_urlNo
created_atNo
expired_atNo
request_idYes
status_urlNo
destinationNo
resend_pathNo
short_url_asciiNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "id": "example"
      +  }
      +]
    • addedInput schema / properties / id / description
      Added value: +"Short code / link id. disable_link is not available yet; this call does not disable the link."
  4. Changed17 schema fields changed
    • removedInput schema / properties / id / description
      Removed value: -"Short code / link id you own"
    • addedOutput schema / properties / code / const
      Added value: +"FEATURE_NOT_AVAILABLE"
    • removedOutput schema / properties / created_at
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / destination
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / error / const
      Added value: +"FEATURE_NOT_AVAILABLE"
    • addedOutput schema / properties / feature
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / id
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / ok / const
      Added value: +false
    • addedOutput schema / properties / retryable / const
      Added value: +false
    • removedOutput schema / properties / short_url
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / short_url_ascii
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / state
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / status_url
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / title
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / tool
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / type
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "request_id"
      -]New value: +[
      +  "ok",
      +  "error",
      +  "code",
      +  "feature",
      +  "tool",
      +  "message",
      +  "request_id",
      +  "retryable"
      +]
  5. Changed17 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Short code / link id you own"
    • removedOutput schema / properties / code / const
      Removed value: -"FEATURE_NOT_AVAILABLE"
    • addedOutput schema / properties / created_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / destination
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / error / const
      Removed value: -"FEATURE_NOT_AVAILABLE"
    • removedOutput schema / properties / feature
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / ok / const
      Removed value: -false
    • removedOutput schema / properties / retryable / const
      Removed value: -false
    • addedOutput schema / properties / short_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / short_url_ascii
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / state
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / status_url
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / title
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / tool
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / type
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "error",
      -  "code",
      -  "feature",
      -  "tool",
      -  "message",
      -  "request_id",
      -  "retryable"
      -]New value: +[
      +  "ok",
      +  "request_id"
      +]
  6. Changed2 schema fields changed
    • removedOutput schema / properties / soft_c_state
      Removed value: -{
      -  "const": "not_live",
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "error",
      -  "code",
      -  "feature",
      -  "tool",
      -  "message",
      -  "soft_c_state",
      -  "request_id",
      -  "retryable"
      -]New value: +[
      +  "ok",
      +  "error",
      +  "code",
      +  "feature",
      +  "tool",
      +  "message",
      +  "request_id",
      +  "retryable"
      +]
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the authorization scope, the verified-email requirement, and precisely what is affected (both short link and QR stop redirecting). It does repeat idempotency, which idempotentHint already declares, and does not say whether disabling is reversible via update_link, keeping it below 5.

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?

The content is front-loaded with purpose, then requirements, then behavior, and every sentence carries information. The bilingual duplication doubles the length and the idempotency sentence restates what annotations already declare, a minor redundancy.

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?

With an output schema present and rich annotations covering safety and idempotency, the description supplies the remaining essentials: ownership, scope, verified email, and the user-visible effect. Only reversibility/enable-path information is missing for a destructive operation.

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 single id parameter is already documented as a short code or link id. The description only reinforces the ownership constraint ('a link you own') and adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('disable a link you own') and states the concrete effect (short link and QR code stop redirecting), which implicitly separates it from update_link. It does not explicitly name a sibling to contrast with, so it falls just short of 5.

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 states clear preconditions for use: the caller must own the link, hold the links:disable scope, and have a verified email. It gives no explicit when-not or alternative-path guidance (e.g., use update_link to change settings instead), so usage context is strong but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources