Skip to main content
Glama
FlywheelStudio

ULink MCP Server

Delete Link

delete_link
Destructive

Permanently deletes a link by its unique ID. This action is irreversible, and the short URL immediately stops working.

Instructions

Permanently delete a link. This is irreversible and the short URL will stop working immediately. Use with caution.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkIdYesThe unique identifier of the link to delete
Behavior5/5

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

The description adds significant behavioral context beyond the destructiveHint annotation: it explicitly states irreversibility and immediate impact on the short URL. This gives the agent a clear understanding of the consequences, enhancing transparency.

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?

The description is concise and front-loaded with the action, followed by two short sentences that each add value: consequences and a cautionary note. No redundant or irrelevant information is present.

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

Completeness5/5

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

For a simple single-parameter tool with a clear destructive annotation, the description is complete. It covers the core action, the irreversible impact, and the immediate effect, which fully equips the agent to select and invoke the tool appropriately.

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?

The input schema already provides a complete description for the only parameter (linkId: 'The unique identifier of the link to delete'), covering 100% of parameter semantics. The description adds no additional parameter information, so a baseline score of 3 is appropriate.

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 clearly states the tool's function with a specific verb and resource: 'Permanently delete a link.' This distinguishes it from sibling tools like update_link, create_link, and list_links by emphasizing the destructive and permanent nature of the action.

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?

The description provides clear context by noting the action is irreversible and the short URL will stop working immediately, alongside the warning 'Use with caution.' This implies when the tool should be used (for permanent deletion) without explicitly naming alternatives, but the context is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FlywheelStudio/ulink-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server