Skip to main content
Glama

Linq.es MCP Server

List Shortlinks

list_shortlinks
Read-onlyIdempotent

Lists standalone ultra-short redirect links (https://linq.es/s/:code) owned by the authenticated user, optionally filtered by associated 'profile' handle, including click counts, iOS/Android routing overrides, and UTM campaign tags. When to use: call this to audit /s/:code shortlinks, check click totals, or verify existing vanity slugs before calling create_shortlink; use list_profile_links instead for buttons displayed on a https://linq.es/ Link-in-Bio page. Prerequisites: requires Bearer lnq_live_ Pro authentication; if filtering by 'profile', call list_profiles first when handles are unknown. Validation: optional 'profile' trims whitespace; omitting 'profile' returns all shortlinks owned by the user across every profile. Side effects: read-only and idempotent; modifies no data. Returns: JSON text with {totalShortLinks, totalClicks, links: [{code, targetUrl, iosUrl, androidUrl, title, owner, profile, active, createdAt, updatedAt, expiresAt, isPasswordProtected, clickCount, utmSource, utmMedium, utmCampaign, utmTerm, utmContent}]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_shortlinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoOptional Linq.es profile handle to filter shortlinks associated with a specific profile; omit to list all account shortlinks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / profile / description
      Previous value: -"Optional profile handle to filter shortlinks"New value: +"Optional Linq.es profile handle to filter shortlinks associated with a specific profile; omit to list all account shortlinks."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses the Bearer authentication requirement, optional profile whitespace trimming, omission behavior, and read-only idempotent side effects. The return shape is also described in enough detail to set expectations without an output schema.

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?

The description is front-loaded with purpose, usage, and prerequisites, then validation, side effects, and returns. It is somewhat long because it enumerates every returned field, but the structure is clear and the content is relevant.

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?

There is no output schema, so the return-shape explanation is valuable, and the authentication, filtering, and side-effect details cover what an agent needs to call the tool correctly. Nothing critical is missing for a one-parameter read-only list operation.

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 profile parameter is already documented. The description still adds useful semantics: whitespace trimming and the fact that omitting profile returns shortlinks across every profile.

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 gives a precise verb and resource: it lists standalone ultra-short redirect links at /s/:code owned by the authenticated user. It immediately distinguishes these from profile-page links by naming list_profile_links as the sibling for that different resource.

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?

It explicitly says when to use this tool—auditing /s/:code shortlinks, checking click totals, or verifying slugs before create_shortlink—and when to use the alternative list_profile_links for Link-in-Bio buttons. It also gives a prerequisite to call list_profiles first when handles are unknown.

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.