Skip to main content
Glama

Get link · 查询单条链接(短.在线)

get_link
Read-onlyIdempotent

按 id 查询当前授权账号拥有的链接。需要已注册账号。公开状态查询用 resolve_short_url。 Fetch one owned link by id. A registered account is required. For a public status check, use resolve_short_url.

Input Schema

NameRequiredDescriptionDefault
idYesShort code or link id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Short code / link id"New value: +"Short code or link id."
  2. Changed4 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -false
    • addedOutput schema / oneOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "created_at": {
      +        "type": "string"
      +      },
      +      "destination": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "ok": {
      +        "const": true,
      +        "type": "boolean"
      +      },
      +      "request_id": {
      +        "type": "string"
      +      },
      +      "short_url": {
      +        "type": "string"
      +      },
      +      "short_url_ascii": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "const": "active",
      +        "type": "string"
      +      },
      +      "status_url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "ok",
      +      "request_id",
      +      "id",
      +      "state",
      +      "created_at",
      +      "status_url",
      +      "short_url",
      +      "short_url_ascii",
      +      "destination"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "created_at": {
      +        "type": "string"
      +      },
      +      "expired_at": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "ok": {
      +        "const": true,
      +        "type": "boolean"
      +      },
      +      "request_id": {
      +        "type": "string"
      +      },
      +      "state": {
      +        "enum": [
      +          "quarantined",
      +          "disabled",
      +          "blocked",
      +          "expired"
      +        ],
      +        "type": "string"
      +      },
      +      "status_url": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "ok",
      +      "request_id",
      +      "id",
      +      "state",
      +      "created_at",
      +      "status_url",
      +      "type",
      +      "title",
      +      "code"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "code": {
      +        "type": "string"
      +      },
      +      "error": {
      +        "type": "string"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "ok": {
      +        "const": false,
      +        "type": "boolean"
      +      },
      +      "request_id": {
      +        "type": "string"
      +      },
      +      "retryable": {
      +        "type": "boolean"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "ok",
      +      "request_id",
      +      "error",
      +      "code",
      +      "message",
      +      "type",
      +      "title",
      +      "retryable"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "code": {
      -    "type": "string"
      -  },
      -  "created_at": {
      -    "type": "string"
      -  },
      -  "destination": {
      -    "type": "string"
      -  },
      -  "error": {
      -    "type": "string"
      -  },
      -  "id": {
      -    "type": "string"
      -  },
      -  "message": {
      -    "type": "string"
      -  },
      -  "ok": {
      -    "type": "boolean"
      -  },
      -  "request_id": {
      -    "type": "string"
      -  },
      -  "retryable": {
      -    "type": "boolean"
      -  },
      -  "short_url": {
      -    "type": "string"
      -  },
      -  "short_url_ascii": {
      -    "type": "string"
      -  },
      -  "state": {
      -    "type": "string"
      -  },
      -  "status_url": {
      -    "type": "string"
      -  },
      -  "title": {
      -    "type": "string"
      -  },
      -  "type": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "ok",
      -  "request_id"
      -]
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "id": "example"
      +  }
      +]
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: ownership scoping to the current authorized account and the registered-account authentication requirement. It does not discuss not-found behavior, but the output schema reduces that burden.

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 description is front-loaded and wastes little space, but the Chinese and English text duplicate the same information. That duplication is understandable for a bilingual tool but prevents a top score for conciseness.

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?

Given the simple one-parameter read operation, rich annotations, full schema coverage, and the presence of an output schema, the description contains everything an agent needs: purpose, ownership scope, auth requirement, and the alternative for public checks.

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?

There is only one parameter and schema description coverage is 100%, with the schema itself defining 'id' as 'Short code or link id.' The description reinforces that the lookup is by id and owned by the account but adds no syntax or format details beyond the schema.

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 ('Fetch one owned link by id') and clearly scopes it to links owned by the current authorized account. It distinguishes itself from the sibling resolve_short_url by naming it as the public-status alternative.

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?

Explicitly states the prerequisite ('A registered account is required') and the alternative for a different use case ('For a public status check, use resolve_short_url'). This gives clear when-to-use and when-not-to-use guidance.

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