Skip to main content
Glama

List links · 列出链接(短.在线)

get_links
Read-onlyIdempotent

列出当前账号拥有的短链。cursor 与 limit 同 GET /v1/links。需要 links:read。 List links this account owns. cursor and limit match GET /v1/links. Requires links:read.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 20
    },
    "name": "get_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, an integer from 1 to 100. Default 50. Same as GET /v1/links.
cursorNoPage cursor from next_cursor. Omit for the first page.

Output Schema

NameRequiredDescriptionDefault
okYes
codeNo
toolNo
typeNo
errorNo
itemsYes
titleNo
featureNo
messageNo
retryableNo
request_idYes
next_cursorYes
resend_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cursor": "example",
      +    "limit": 20
      +  }
      +]
    • addedInput schema / properties / cursor / description
      Added value: +"Optional page cursor. get_links is not available yet; this call does not list links."
    • addedInput schema / properties / limit / description
      Added value: +"Optional page size, an integer from 1 to 100. get_links is not available yet; this call does not list links."
  4. Changed11 schema fields changed
    • removedInput schema / properties / cursor / description
      Removed value: -"Pagination cursor from previous next_cursor"
    • removedInput schema / properties / limit / description
      Removed value: -"Page size (1–100, default 50)"
    • addedOutput schema / properties / code / const
      Added value: +"FEATURE_NOT_AVAILABLE"
    • addedOutput schema / properties / error / const
      Added value: +"FEATURE_NOT_AVAILABLE"
    • addedOutput schema / properties / feature
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / items
      Removed value: -{
      -  "items": {
      -    "additionalProperties": {},
      -    "propertyNames": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • removedOutput schema / properties / next_cursor
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • addedOutput schema / properties / ok / const
      Added value: +false
    • addedOutput schema / properties / retryable / const
      Added value: +false
    • addedOutput schema / properties / tool
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "ok",
      -  "request_id"
      -]New value: +[
      +  "ok",
      +  "error",
      +  "code",
      +  "feature",
      +  "tool",
      +  "message",
      +  "request_id",
      +  "retryable"
      +]
  5. Changed11 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor from previous next_cursor"
    • addedInput schema / properties / limit / description
      Added value: +"Page size (1–100, default 50)"
    • removedOutput schema / properties / code / const
      Removed value: -"FEATURE_NOT_AVAILABLE"
    • removedOutput schema / properties / error / const
      Removed value: -"FEATURE_NOT_AVAILABLE"
    • removedOutput schema / properties / feature
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / items
      Added value: +{
      +  "items": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / next_cursor
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • removedOutput schema / properties / ok / const
      Removed value: -false
    • removedOutput schema / properties / retryable / const
      Removed value: -false
    • removedOutput schema / properties / tool
      Removed 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.6/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 value beyond that by stating the required OAuth scope (links:read) and by pinning pagination semantics to GET /v1/links, which tells an agent the paging contract matches a known REST endpoint. It stops short of describing default page size or ordering, but the schema covers the default.

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

Conciseness3/5

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

Front-loaded with the resource scope, which is correct. However, the entire content is duplicated verbatim in Chinese and English, so roughly half the text is redundant for any given reader; the scope and pagination facts could be expressed in a single sentence per language without loss.

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?

This is a simple two-optional-parameter read tool with an output schema, so return values need not be explained. Scope, auth requirement, and pagination source are all present. Only the absence of sibling routing guidance keeps it from being fully complete.

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 description coverage is 100% and both parameters already document their range, default, and cursor origin from next_cursor. The description's 'cursor and limit match GET /v1/links' adds a useful cross-reference for agents that know the REST contract, but nothing about the parameters that isn't already in the schema. Baseline 3 applies when the schema carries the load.

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?

States a specific verb+resource with scope: list short links owned by the current account. That scope phrase separates it from get_link (single link) and resolve_short_url, though neither sibling is named explicitly. An agent can identify what it returns without opening the schema.

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

Usage Guidelines3/5

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

Gives a concrete prerequisite (requires links:read) but no explicit routing guidance such as 'use get_link for a single link by id' or 'use resolve_short_url to expand a slug'. Usage is implied by the plural/enumeration nature rather than stated.

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