Skip to main content
Glama

Linq.es MCP Server

Create Shortlink

create_shortlink

Creates an active standalone redirect shortlink at https://linq.es/s/:code with an optional custom vanity slug, smart iOS/Android device redirects, optional profile attribution, and automatic UTM query parameter injection. When to use: choose create_shortlink for standalone shareable redirect URLs used in social posts, newsletters, QR codes, or ad campaigns; use add_profile_link instead to add a visible button to a Link-in-Bio profile page. Prerequisites: requires Bearer lnq_live_ Pro authentication; optionally call list_shortlinks first to check existing slugs or list_profiles to confirm a 'profile' handle. Validation and limits: 'targetUrl' (and optional 'iosUrl', 'androidUrl' when provided) must start with http:// or https://; optional 'code' must be 3-50 characters matching ^[a-zA-Z0-9_-]{3,50}$, must not use reserved system routes (such as admin, api, login, mcp, pricing, explore, tools), and must be globally unique across Linq.es (if 'code' is omitted, a random 6-character alphanumeric slug is generated); enforces the Pro cap of 500 shortlinks per account, returning isError: true on invalid URLs, slug collision, or quota exhaustion. Side effects: non-idempotent (creates a new shortlink when 'code' is omitted, or fails on duplicate 'code') and immediately activates https://linq.es/s/ in Firestore. Returns: JSON text with {status, code, shortUrl, targetUrl, shortlink: {code, targetUrl, iosUrl, androidUrl, title, owner, profile, active, createdAt, updatedAt, clickCount, utmSource, utmMedium, utmCampaign, utmTerm, utmContent}}.

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": {
      "targetUrl": "<targetUrl>"
    },
    "name": "create_shortlink"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional custom vanity slug for https://linq.es/s/<code> (3-50 letters, digits, hyphens, or underscores; omit to auto-generate a unique 6-char code).
titleNoOptional internal label to identify the shortlink in dashboard listings and analytics.
iosUrlNoOptional http:// or https:// destination override redirected to when opened on iOS/iPadOS devices.
profileNoOptional owned Linq.es profile handle to associate this shortlink with for filtering in list_shortlinks.
utmTermNoOptional utm_term paid keyword parameter appended to the destination URL on redirect.
targetUrlYesDefault destination URL starting with http:// or https:// where visitors are redirected.
utmMediumNoOptional utm_medium query parameter appended to the destination URL on redirect (e.g. 'social', 'cpc', 'qr').
utmSourceNoOptional utm_source query parameter appended to the destination URL on redirect (e.g. 'newsletter', 'instagram').
androidUrlNoOptional http:// or https:// destination override redirected to when opened on Android devices.
utmContentNoOptional utm_content variant parameter appended to the destination URL on redirect (e.g. 'header_cta').
utmCampaignNoOptional utm_campaign query parameter appended to the destination URL on redirect (e.g. 'spring_launch').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by explaining non-idempotency mechanics (a new shortlink is created when 'code' is omitted, or the call fails on a duplicate 'code'), immediate activation in Firestore, the 500-shortlink Pro cap, and the isError:true failure conditions for invalid URLs, slug collisions, or quota exhaustion. It does not discuss rate limiting or whether created shortlinks can be deactivated by a sibling tool, so it stops short of 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.

Conciseness4/5

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

Dense but well organized with labeled clauses (When to use, Prerequisites, Validation and limits, Side effects, Returns), so an agent can parse the section it needs. It errs toward over-inclusion—the full 'Returns' object listing duplicates what the call will literally return—but that data substitutes for an absent output schema.

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 an 11-parameter, non-idempotent mutation with no output schema, the description covers auth, limits, side effects, failure modes, and return shape, leaving little an agent needs to infer. The absence of guidance on downstream management (e.g., delete/disable via siblings) is the main residual gap.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: the reserved-route blocklist (admin, api, login, mcp, pricing, explore, tools), the global uniqueness requirement across Linq.es, and the auto-generated 6-character fallback. It does not document the individual utm* fields' expected format beyond what the schema descriptions already say, keeping it from a 5.

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 ('Creates an active standalone redirect shortlink at https://linq.es/s/:code') and enumerates its distinguishing capabilities: custom vanity slug, iOS/Android redirects, profile attribution, and UTM injection. It explicitly contrasts with the sibling add_profile_link ('visible button to a Link-in-Bio profile page'), so an agent can differentiate without opening schemas.

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?

Provides an explicit 'When to use' clause with concrete scenarios (social posts, newsletters, QR codes, ad campaigns) and names the alternative tool plus the condition that selects it. Prerequisites are spelled out (Bearer lnq_live_<key> Pro auth) along with an optional pre-check step via list_shortlinks or list_profiles.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources