好縮 Short

Get Link Info

get_link_info

Read-onlyIdempotent

Retrieve metadata and status of a specific short link by its short code or full short URL (compatible with get_url_info). Returns original URL, webpage title, click count, tags, password status, and creation/expiration time.

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": {
      "code": "<code>"
    },
    "name": "get_link_info"
  }
}

Input Schema

Name	Required	Description	Default
`code`	Yes	Short code or full short URL (e.g., shgBe2 or https://s.gooo.name/shgBe2)

Output Schema

Name	Required	Description
`title`	No	Webpage title
`clicks`	No	Total click count
`link_id`	Yes	Short code identifier
`is_custom`	No	Whether custom code
`is_public`	No	Whether visible on public profile
`short_url`	Yes	Full short URL
`created_at`	No	Creation timestamp (ISO 8601)
`short_code`	No	Short code
`has_password`	No	Whether password-protected
`original_url`	Yes	Original destination URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that password status and expiration are surfaced, which is modest extra context, but says nothing about behavior for a nonexistent code, auth requirements, or error cases.

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?

One sentence, front-loaded with the verb and resource, followed by the identifier forms and return fields; no filler. Slight redundancy in enumerating return values that the output schema already defines.

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, rich annotations, and a single well-documented parameter, the definition covers nearly everything needed to invoke it. The only real gap is the absence of any note on what happens when the code does not resolve.

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 parameter is documented with an example in the schema itself. The description merely restates that the code may be a short code or a full short URL, adding no format or validation 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.

Purpose5/5

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

States a specific verb (retrieve metadata and status) and resource (a specific short link) plus the accepted identifier forms, and lists the returned fields. An agent can distinguish this single-link lookup from list_my_links or get_link_analytics 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?

The phrase 'compatible with get_url_info' hints at an aliasing relationship, but that tool is not among the siblings, so the routing value is unclear. There is no explicit statement of when to prefer this over get_link_analytics or list_my_links, leaving usage to inference from the tool name.

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

All 好縮 Short 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?