kualat-mcp

Update a link

update_link

Modify an existing shortened link's destination, alias, title, expiry, password, or note; include every optional field you want to preserve because omitted settings are replaced.

Instructions

Change a link. The API replaces the optional settings it does not receive, so pass every field you want to keep.

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": {
      "id": "<id>"
    },
    "name": "update_link"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Link id.
`url`	No	New destination URL.
`title`	No	Meta title.
`custom`	No	New custom alias.
`expiry`	No	Expiry date, ISO 8601 or "YYYY-MM-DD HH:MM:SS".
`password`	No	New password, or an empty string to remove it.
`description`	No	Internal note.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true; the description adds the non-obvious PUT-style semantics where any optional field not sent is reset. That is a genuinely valuable disclosure an agent cannot get from annotations or schema, and it hints at a data-loss hazard that destructiveHint=false would otherwise hide. It does not cover auth needs, error behavior, or return values, so it is not a 5.

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, zero filler. The identity of the operation is front-loaded and the destructive-omission caveat follows immediately where an agent would read it before building arguments.

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?

For a 7-parameter mutation tool with no output schema, the one behavior an agent must know to avoid silently wiping fields is present. Missing pieces are minor: what a successful response contains, whether the id itself is mutable, and permission requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but "pass every field you want to keep" adds meaning the schema does not: omitting url, title, custom, expiry, password, or description resets them rather than leaving them untouched. That reframes how all six optional parameters must be treated when calling the tool.

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?

"Change a link" pairs a mutation verb with a specific resource, so an agent can distinguish it from get_link, list_links, and delete_link without opening the schema. It stops short of naming any sibling or stating the scope of what can be changed, so it is clear but not differentiated.

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 second sentence gives implicit usage rules by warning that omitted optional fields are replaced, which tells the agent how to call it safely. However, there is no explicit when-to-use guidance, no mention of alternatives such as delete_link plus shorten_link for a full replacement, and no prerequisites described.

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

Deploy Server