Skip to main content
Glama

Linq.es MCP Server

Add Profile Link

add_profile_link

Creates a new active link card or header social icon on a Linq.es Link-in-Bio profile, with automatic rich media type detection (YouTube, Spotify, etc.), optional highlight badge, iOS/Android smart routing, scheduled visibility window, countdown badge, and live click counter badge. When to use: choose add_profile_link to append one new link to a profile page; use update_profile_link to edit or toggle an existing link by 'key', import_bio_links to bulk-import from an external bio page, or create_shortlink to create a standalone linq.es/s/:code redirect. Prerequisites: requires Bearer lnq_live_ Pro authentication and an owned 'profile' handle (call list_profiles first if unknown). Validation and limits: 'title' must be non-empty; 'url' (and optional 'iosUrl', 'androidUrl' when provided) must use http:// or https://; optional 'scheduleStart' and 'scheduleEnd' must be valid RFC3339 timestamps (e.g. '2026-10-15T14:00:00Z'); enforces the Pro quota of 100 links per profile, returning isError: true on validation or quota errors. Side effects: non-idempotent (each call inserts a new Firestore link document with active: true) and immediately purges in-memory, HTML, and CDN caches for https://linq.es/. Returns: JSON text with {status, message, profile, title, url}; call list_profile_links afterward if you need the newly generated 'key'.

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

Input Schema

NameRequiredDescriptionDefault
urlYesDefault destination URL starting with http:// or https:// used for desktop and fallback visitors.
titleYesVisible button label or social network name displayed on the profile (e.g. 'Download on iOS & Android').
iosUrlNoOptional http:// or https:// override URL opened specifically for iPhone and iPad visitors (e.g. Apple App Store URL).
profileYesOwned Linq.es profile handle to append the link to (e.g. 'alex').
isSocialNoSet true to render as a compact social icon in the profile header instead of a full-width link button (defaults to false).
badgeTextNoOptional short pill badge label displayed on the link card (e.g. 'NEW', 'HOT', 'LIVE').
androidUrlNoOptional http:// or https:// override URL opened specifically for Android visitors (e.g. Google Play URL).
scheduleEndNoOptional RFC3339 UTC timestamp when the link automatically hides from the public profile (e.g. '2026-10-20T14:00:00Z').
scheduleStartNoOptional RFC3339 UTC timestamp when the link becomes publicly clickable (e.g. '2026-10-15T14:00:00Z').
showCountdownNoSet true to render a live countdown timer on the public card until 'scheduleStart' is reached (defaults to false).
showClickBadgeNoSet true to display a public click-count social-proof badge on the link card (defaults to false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations that already declare non-read-only, non-idempotent, non-destructive behavior, the description discloses the concrete side effects: each call inserts a new Firestore document with active true and purges in-memory, HTML, and CDN caches. It additionally states Bearer authentication requirements, the 100-link Pro quota, error behavior, and the return shape.

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, then usage, prerequisites, validation, side effects, and returns. It is dense but well organized; some validation details duplicate the schema, and the first sentence carries a long feature list, but no sentence is clearly irrelevant.

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 an 11-parameter mutation tool with no output schema, the definition covers authentication, prerequisite discovery, validation, quota limits, side effects, cache purging, and the returned JSON fields. It gives an agent everything needed to invoke the tool safely and understand the immediate outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, so the baseline is 3. The description adds some cross-parameter validation context and maps optional capabilities such as badges, routing, and scheduling to the request, but it largely restates constraints already present in the schema.

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 states a specific verb and resource: it creates a new active link card or header social icon on a Linq.es Link-in-Bio profile. It also enumerates the distinctive capabilities such as media detection, smart routing, scheduling, and badge types, so an agent can distinguish it from sibling tools without opening the 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?

It gives explicit when-to-use guidance: choose this tool to append one new link, and use update_profile_link to edit/toggle, import_bio_links for bulk import, or create_shortlink for a standalone redirect. It also states the prerequisite authentication and profile ownership, including calling list_profiles first if the handle is 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.

Resources