好縮 Short

Create Short URL

create_short_url

Create a short link (s.gooo.name) for an HTTP or HTTPS URL (compatible with shorten_url). Use when the user explicitly requests URL shortening, custom short codes, password protection, or link tagging. Automatically associates the link with the user's account when authenticated.

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": {
      "url": "<url>"
    },
    "name": "create_short_url"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Target HTTP or HTTPS URL to shorten (e.g., https://github.com/openai/openai-node)
`tags`	No	Optional category tags (e.g., ["AI", "work"])
`channel`	No	Optional AI client identifier (e.g., chatgpt, codex, gemini, cursor, claude)
`password`	No	Optional password to protect the short link upon redirect
`session_id`	No	Optional session identifier when not using OAuth Bearer token
`custom_code`	No	Optional custom short code (at least 5 alphanumeric, hyphen, or underscore characters, e.g., my-doc)

Output Schema

Name	Required	Description
`title`	No	Extracted webpage title
`channel`	No	Recorded creation channel
`link_id`	Yes	Unique link identifier / short code
`is_custom`	No	Whether a custom code was used
`short_url`	Yes	Generated short URL (https://s.gooo.name/...)
`short_code`	No	Short code
`has_password`	No	Whether password protection is enabled
`original_url`	No	Target original URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds genuinely new behavior — the link is auto-associated with the user's account when authenticated — and hints at an unauthenticated path via the session_id parameter. It does not disclose failure modes for a taken custom_code or why check_code_availability exists as a sibling, leaving some behavioral risk undisclosed.

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?

Three sentences, purpose first, then usage, then authentication behavior — well front-loaded. The clause "Use when the user explicitly requests URL shortening" is mildly redundant with the opening sentence, but it earns its place by pairing the trigger with the optional features.

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, return values need not be explained, and annotations cover the mutation safety profile. The description covers purpose, triggers, and account linkage for a 6-parameter tool. It is slightly incomplete on the custom-code collision path and the auth/session_id relationship, which an agent would want before calling.

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%, so every parameter including custom_code's character rules and channel's client identifiers is already documented. The description restates the interesting parameter concepts (custom codes, password protection, tags) but adds no syntax, constraints, or interaction rules beyond the schema, 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 opens with a specific verb+resource ("Create a short link") and names the concrete service domain (s.gooo.name) plus the accepted input type (HTTP/HTTPS URL). It also notes compatibility with shorten_url, which disambiguates it from the update/delete/analytics siblings at a glance.

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 gives an explicit trigger condition: use when the user asks for URL shortening, custom short codes, password protection, or tagging. That maps directly to the optional parameters. It stops short of stating when NOT to use it or naming a concrete alternative tool (check_code_availability for code conflicts, update_short_url for edits), so it is clear but not complete guidance.

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?