Skip to main content
Glama

Linq.es MCP Server

List Link-in-Bio Profiles

list_profiles
Read-onlyIdempotent

Lists every Linq.es Link-in-Bio profile owned by the authenticated user. When to use: call this first to discover valid 'profile' handles before calling get_profile_analytics, list_profile_links, add_profile_link, update_profile_link, import_bio_links, or list_leads; use list_shortlinks instead for standalone linq.es/s/:code redirects. Prerequisites: requires an authenticated Linq.es Pro credential via Authorization: Bearer lnq_live_ on tools/call. Validation: requires no input parameters; returns isError: true if the authenticated user account cannot be loaded. Side effects: read-only and idempotent; modifies no data or caches. Returns: JSON text with {username, subscription, profiles: [{profileName, name, headline, theme, listedInExplore, publicUrl, viewCount}]}.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint, idempotentHint and destructiveHint=false, but the description adds information the agent cannot get from them: the required Bearer lnq_live_<key> Pro credential on tools/call, the failure mode (isError: true when the account cannot be loaded), and confirmation that no data or caches are modified.

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?

Labeled sections (When to use, Prerequisites, Validation, Side effects, Returns) make it scannable and front-loaded. The 'read-only and idempotent' clause partly restates the annotations, which is a small redundancy in an otherwise tight definition.

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?

No output schema exists, so the description supplies the return contract itself — the top-level {username, subscription, profiles:[...]} shape with the per-profile field list — and covers auth, failure mode, and side effects. Nothing an agent needs in order to call this correctly is missing.

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?

With zero input parameters the baseline is 4; the description correctly states 'requires no input parameters', which is consistent with the empty schema and warns the agent not to synthesize arguments. There is no additional parameter meaning to convey.

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 every Linq.es Link-in-Bio profile owned by the authenticated user') and scopes it to the authenticated user, which immediately separates it from list_shortlinks (standalone linq.es/s/:code redirects) named later in the text.

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 'call this first' and enumerates the downstream tools that depend on its output (get_profile_analytics, list_profile_links, add_profile_link, update_profile_link, import_bio_links, list_leads), then names the sibling to use instead when the target is a shortlink. When-to-use and when-not-to-use are both present.

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