短.在线

Get link · 查询单条链接（短.在线）

get_link

Read-onlyIdempotent

按 id 查询一条链接，仅限已登录账户自己的链接。需要已注册账户。公开状态请用 resolve_short_url。 Fetch one link by id, only a link owned by the signed-in account. A registered account is required. For a public status check, use resolve_short_url.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Short code / link id

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

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"
-]

Changed1 schema field changedOct 1, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "id": "example"
+  }
+]
```
First observedSep 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two pieces of context the annotations do not carry: an authentication prerequisite (registered account) and a permission/ownership constraint (only your own links), which materially affects whether a call will succeed.

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 access scope and the alternative tool are front-loaded, and each sentence earns its place. The only inefficiency is that the same content is rendered twice in Chinese and English, roughly doubling the payload, though the parallel structure keeps it scannable.

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 annotations covering the safety profile and an output schema present, the description need not explain return values, and it correctly focuses on auth, ownership scope, and tool routing. It is complete enough to call correctly; only edge-case behavior (e.g., what happens when the id is not owned or not found) is left unspecified.

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 a single parameter with 100% schema description coverage ("Short code / link id", minLength 1, maxLength 64), so the schema already does the heavy lifting. The description supplies no additional syntax, format, or origin guidance for the id beyond what the schema states, so the baseline of 3 applies.

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 gives a specific verb + resource + selector ("查询一条链接" / "Fetch one link by id") and immediately bounds the scope to links owned by the signed-in account. It also names the sibling tool it is not (resolve_short_url), so an agent can distinguish get_link from resolve_short_url without opening 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 Guidelines5/5

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

It states the preconditions (registered account required, ownership scope) and explicitly routes the agent to the alternative for the public case: "公开状态请用 resolve_short_url" / "For a public status check, use resolve_short_url." When-to-use and when-not-to-use are both present, with the alternative named.

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

All 短.在线 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?