kualat-mcp

Shorten a link

shorten_link

Create a shortened URL with optional custom alias, branded domain, expiry, password, and title; returns the short URL, alias, and link ID.

Instructions

Create a short link on the account. Returns the short URL, alias and link id.

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": "shorten_link"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Destination URL, including the scheme.
`title`	No	Meta title shown in link previews.
`custom`	No	Readable alias instead of a generated one.
`domain`	No	Branded domain connected to the account.
`expiry`	No	Expiry date, ISO 8601 or "YYYY-MM-DD HH:MM:SS".
`password`	No	Password visitors must enter before the redirect.
`description`	No	Internal note about the link.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write/non-destructive profile is covered. The description adds value by stating what is returned (short URL, alias, link id), which matters since there is no output schema, but it says nothing about failure modes such as duplicate custom aliases, invalid domains, or whether the generated alias is guaranteed unique.

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

Conciseness5/5

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

Two short sentences with zero filler, front-loading the action and then the return values. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter create tool with no output schema, the description is minimally adequate: the return values are disclosed and the write semantics are clear from annotations. However, it omits any account/domain prerequisites or error behavior that an agent would want before invoking a mutating call.

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%, so all seven parameters (url, title, custom, domain, expiry, password, description) are already documented in the schema. The description adds no additional meaning about parameter interactions, such as whether 'custom' must be unique or whether 'domain' must come from list_domains; baseline 3 applies.

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?

The description names a specific verb and resource ('Create a short link on the account'), which is unambiguous and clearly distinct from the read/update/delete siblings. It stops short of explicitly contrasting itself with any named alternative, but the operation itself is unmistakable.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as update_link for modifying an existing link. The agent must infer the use case entirely 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.

Deploy Server