Skip to main content
Glama

Linq.es MCP Server

Import External Bio Links

import_bio_links

Fetches a public external Link-in-Bio page (such as Linktree, Beacons, Bio.link, Carrd, or a personal links page) over HTTP/HTTPS, extracts outbound links from its HTML, and appends them as active link cards on a Linq.es profile. When to use: choose this for bulk migration from an external public bio URL; use add_profile_link instead when adding individual links with custom badges, smart routing, or schedules. Prerequisites: requires Bearer lnq_live_ Pro authentication and an owned 'profile' handle (call list_profiles first if unknown). Validation and safety limits: auto-prepends https:// if the scheme is omitted; blocks loopback, private, link-local, and cloud-metadata addresses (SSRF protection); enforces a 6-second fetch timeout, at most 3 redirects, and a 512 KiB HTML read cap; imports only up to remaining capacity under the 100-link Pro per-profile limit, returning isError: true if the profile is unowned or the remote page fails to load. Side effects: performs an open-world outbound HTTP GET request, inserts new Firestore link documents non-idempotently (re-running against the same source URL appends duplicates), and purges the target profile's public caches. Returns: JSON text with {status, profile, importedCount, message}.

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>",
      "url": "<url>"
    },
    "name": "import_bio_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP/HTTPS URL of the external bio page to scrape outbound links from (e.g. 'https://linktr.ee/username').
profileYesOwned target Linq.es profile handle where extracted links will be appended (e.g. 'alex').

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 flag openWorldHint=true and idempotentHint=false, but the description goes well beyond them: SSRF blocking of loopback/private/metadata addresses, 6-second timeout, 3-redirect cap, 512 KiB read limit, 100-link capacity enforcement, and the concrete fact that re-running appends duplicates. It also discloses the cache purge and the isError conditions (unowned profile, failed remote load), which annotations cannot express.

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?

Front-loaded with purpose before the 'When to use' and 'Prerequisites' labels, and essentially every sentence carries operational content. It is dense to the point of being a single run-on block, which slightly hurts scannability, but no sentence is filler.

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?

For a two-parameter mutating tool with no output schema, the definition still covers purpose, alternative routing, auth prerequisites, network safety limits, capacity constraints, side effects, and the return payload shape {status, profile, importedCount, message}. An agent has everything needed to call it correctly and predict the outcome.

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 both parameters are already documented, but the description adds real behavioral meaning: scheme omission triggers an automatic https:// prepend, and the profile handle must be owned by the caller. That extra context on URL normalization and ownership is genuinely beyond the schema, though it stops short of covering the minLength bounds.

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 chain (fetches, extracts, appends) with the resource (external Link-in-Bio page) and the destination (Linq.es profile), naming concrete examples like Linktree, Beacons, and Carrd. It explicitly contrasts with add_profile_link, so an agent can select between them 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?

Provides an explicit 'When to use' clause for bulk migration and names the alternative tool for the contrasting case (individual links with badges, smart routing, schedules). Prerequisites are spelled out (Bearer lnq_live_<key> Pro auth, owned profile handle, call list_profiles first if unknown), leaving nothing to inference.

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