Skip to main content
Glama
Sign In
LinkPilot MCP Server

LinkPilot MCP Server

Official
by TetraCoreHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create a short link

create_short_link

Shorten a public URL into a branded link with click tracking, plus optional custom slug, title, tags, or domain.

Instructions

Shorten a URL to a branded LinkPilot short link with click tracking. For public URLs. To share something private, use create_secret_link instead.

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_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe destination URL, including https://.
slugNoCustom path, for example 'launch'. Omit for a generated one.
tagsNoTags for filtering in the dashboard.
titleNoA label, shown in the dashboard only.
domainNoA custom domain on the account. Omit for the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety and repeatability profile is covered. The description adds that the resulting link tracks clicks and is intended for public content, but says nothing about slug collisions, rate limits, or whether a created link can be edited/revoked later.

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 sentences with zero filler. The purpose and click-tracking benefit come first, and the sibling routing constraint comes second, matching the reading order an agent needs.

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 create tool with full annotation coverage and a fully documented schema, the description is nearly self-sufficient. The one gap is that with no output schema present, it never says what the call returns (presumably the short URL/slug), which an agent would need to chain a share step.

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% - all five parameters (url, slug, tags, title, domain) are individually documented in the schema with examples and omit-defaults guidance. The description adds no parameter-level detail beyond that, so baseline 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?

States a specific verb and resource ('Shorten a URL to a branded LinkPilot short link'), adds the differentiating capability ('with click tracking'), and scopes it to public URLs. The sibling create_secret_link is named, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('For public URLs') and when-not with the exact alternative to use instead ('To share something private, use create_secret_link instead'). This is a clean conditional routing rule with no inference required.

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

Deploy Server

Other Tools