Skip to main content
Glama
@elido/mcp-server

@elido/mcp-server

Official
by elidoapp

create_link

Shorten destination URLs on the configured workspace and return the short URL with its canonical link record. Optionally set a custom slug, tags, title, or domain.

Instructions

Shorten a URL on the configured workspace. Returns the short URL plus the canonical link record.

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": {
      "destination_url": "<destination_url>"
    },
    "name": "create_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional custom slug.
tagsNo
titleNo
domain_idNoDomain to use. Defaults to the workspace's first verified domain.
destination_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the return shape ("short URL plus the canonical link record"), which is valuable given there is no output schema. However, it omits failure modes such as duplicate or invalid slugs, whether the operation is idempotent, and any authentication or quota requirements.

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 waste; the core action is front-loaded and the return-value sentence earns its place because no output schema exists.

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 five-parameter mutation tool with no annotations and no output schema, the description covers purpose and return value but leaves error behavior, parameter semantics, and prerequisites unaddressed. It is minimally adequate rather than complete.

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

Parameters2/5

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

Schema description coverage is only 40% (slug and domain_id are documented, while tags, title, and destination_url are not) and the description adds no parameter meaning at all. With coverage below 50%, the description should compensate for the undocumented parameters but does not.

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?

States a specific verb and resource: "Shorten a URL on the configured workspace." That clearly separates it from list_links and generate_qr, though it never names a sibling explicitly.

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 or when-not-to-use guidance, no mention of how it relates to list_links or generate_qr, and no prerequisites (such as needing a verified domain) are stated. Usage is only inferable from the purpose sentence.

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