Skip to main content
Glama

Linq.es MCP Server

List Profile Links

list_profile_links
Read-onlyIdempotent

Lists all link buttons and header social icons (both active and inactive) configured on a Linq.es Link-in-Bio profile. When to use: call this to inspect profile links and obtain each link's unique 'key' and current field values before calling update_profile_link or delete_profile_link; use list_shortlinks instead for standalone linq.es/s/:code redirect URLs. Prerequisites: requires Bearer lnq_live_ Pro authentication and a 'profile' handle owned by the caller (discoverable via list_profiles). Validation: returns isError: true if 'profile' is empty or does not belong to the authenticated user. Side effects: read-only and idempotent; does not modify links or caches. Returns: JSON text with {profile, count, links: [{key, title, url, description, active, profile, owner, order, isSocial, sectionId, badgeText, animation, type, scheduleStart, scheduleEnd, showCountdown, showClickBadge, iosUrl, androidUrl, isPasswordProtected, isSensitive, isFeatured, createDate, editDate, analytics: {clickCount, lastClicked}}]}.

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": {
      "profile": "<profile>"
    },
    "name": "list_profile_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesOwned Linq.es profile handle whose link cards and social icons should be listed (e.g. 'alex').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / profile / description
      Previous value: -"Profile handle (e.g. 'alex')"New value: +"Owned Linq.es profile handle whose link cards and social icons should be listed (e.g. 'alex')."
    • addedInput schema / properties / profile / minLength
      Added value: +1
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, but the description adds substantial context: Bearer token requirement, the profile handle must belong to the caller, validation returns isError true for invalid profiles, and it does not modify links or caches. It also discloses the full return shape beyond what the annotations cover.

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 and well organized with when-to-use, prerequisites, validation, side effects, and returns. The return-field list is very long, but it is still structured and purposeful rather than repetitive.

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?

Complete for a one-parameter read tool with no output schema: it explains use, alternatives, prerequisites, validation behavior, side effects, and the returned JSON structure. Nothing material is missing for correct selection or invocation.

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 parameter is already documented. The description adds useful meaning by saying the handle is owned by the caller, must be a profile handle, and can be discovered via list_profiles, plus the error condition when it is empty or unowned.

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: lists all link buttons and header social icons configured on a Link-in-Bio profile, including inactive ones. It also distinguishes itself from list_shortlinks, so an agent can separate profile-link inspection from standalone short-link listing.

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?

Explicitly says when to call it: to inspect links and obtain each link's key and values before update_profile_link or delete_profile_link. It also names list_shortlinks as the alternative for standalone redirect URLs and states the authentication and ownership prerequisites.

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.