Skip to main content
Glama

Linq.es MCP Server

Update Profile Link

update_profile_link
Idempotent

Updates an existing link card or header social icon on a Linq.es Link-in-Bio profile by its unique 'key', while preserving its section placement, animation, and existing schedule timestamps. When to use: choose update_profile_link to change a link's title, URLs, badge, or visibility (set active: false to hide a link non-destructively while keeping its click history); use delete_profile_link only for permanent removal, or add_profile_link to create a new link. Prerequisites: requires Bearer lnq_live_ Pro authentication; call list_profile_links first to obtain 'key' and current values, because omitted optional string fields ('badgeText', 'iosUrl', 'androidUrl') are cleared to empty strings whereas omitted boolean flags ('isSocial', 'showCountdown', 'showClickBadge') retain their stored values. Validation: 'key', 'profile', and 'title' must be non-empty; 'url' (and any non-empty 'iosUrl' or 'androidUrl') must start with http:// or https://; returns isError: true if 'key' does not exist or is not owned by the caller. Side effects: idempotent for identical arguments; overwrites the link document in Firestore and immediately purges the owning profile's multi-layer cache. Returns: JSON text with {status, message, 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": {
      "key": "<key>",
      "profile": "<profile>",
      "title": "<title>",
      "url": "<url>",
      "active": "<active>"
    },
    "name": "update_profile_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesUnique Firestore document key of the link to update, retrieved from list_profile_links.
urlYesUpdated default destination URL starting with http:// or https://.
titleYesUpdated visible button label or social icon title.
activeYesSet true to publish the link on the public profile, or false to hide it without deleting analytics.
iosUrlNoiOS http:// or https:// override URL (pass existing value to keep it, or omit/pass '' to clear iOS routing).
profileYesOwned Linq.es profile handle associated with the link (e.g. 'alex').
isSocialNoOptional boolean controlling whether the item renders as a header social icon; if omitted, preserves the existing stored value.
badgeTextNoHighlight pill badge text (pass existing value to keep it, or omit/pass '' to clear the badge).
androidUrlNoAndroid http:// or https:// override URL (pass existing value to keep it, or omit/pass '' to clear Android routing).
showCountdownNoOptional boolean toggling the countdown timer badge; if omitted, preserves the existing stored value.
showClickBadgeNoOptional boolean toggling the public click-count badge; if omitted, preserves the existing stored value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / active / description
      Previous value: -"Whether the link is active/visible"New value: +"Set true to publish the link on the public profile, or false to hide it without deleting analytics."
    • changedInput schema / properties / androidUrl / description
      Previous value: -"Optional Android destination override URL"New value: +"Android http:// or https:// override URL (pass existing value to keep it, or omit/pass '' to clear Android routing)."
    • addedInput schema / properties / androidUrl / format
      Added value: +"uri"
    • changedInput schema / properties / badgeText / description
      Previous value: -"Optional highlight badge text"New value: +"Highlight pill badge text (pass existing value to keep it, or omit/pass '' to clear the badge)."
    • addedInput schema / properties / badgeText / maxLength
      Added value: +32
    • changedInput schema / properties / iosUrl / description
      Previous value: -"Optional iOS destination override URL"New value: +"iOS http:// or https:// override URL (pass existing value to keep it, or omit/pass '' to clear iOS routing)."
    • addedInput schema / properties / iosUrl / format
      Added value: +"uri"
    • changedInput schema / properties / isSocial / description
      Previous value: -"Whether the link is rendered as a social icon in the header"New value: +"Optional boolean controlling whether the item renders as a header social icon; if omitted, preserves the existing stored value."
    • changedInput schema / properties / key / description
      Previous value: -"Unique key of the link to update"New value: +"Unique Firestore document key of the link to update, retrieved from list_profile_links."
    • addedInput schema / properties / key / minLength
      Added value: +1
    • changedInput schema / properties / profile / description
      Previous value: -"Profile handle that owns the link"New value: +"Owned Linq.es profile handle associated with the link (e.g. 'alex')."
    • addedInput schema / properties / profile / minLength
      Added value: +1
    • changedInput schema / properties / showClickBadge / description
      Previous value: -"True to display a live click counter badge on the public link card"New value: +"Optional boolean toggling the public click-count badge; if omitted, preserves the existing stored value."
    • changedInput schema / properties / showCountdown / description
      Previous value: -"True to show a live countdown badge when scheduleStart is in the future"New value: +"Optional boolean toggling the countdown timer badge; if omitted, preserves the existing stored value."
    • changedInput schema / properties / title / description
      Previous value: -"Updated display title"New value: +"Updated visible button label or social icon title."
    • addedInput schema / properties / title / maxLength
      Added value: +200
    • addedInput schema / properties / title / minLength
      Added value: +1
    • changedInput schema / properties / url / description
      Previous value: -"Updated default destination URL"New value: +"Updated default destination URL starting with http:// or https://."
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / minLength
      Added value: +8
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the asymmetric omission behavior ('badgeText', 'iosUrl', 'androidUrl' cleared to empty strings vs. boolean flags retaining stored values), the auth requirement (Bearer lnq_live_<key> Pro), the write path (overwrites the Firestore document and purges the profile's multi-layer cache), and error semantics (isError:true when the key is missing or unowned). The annotations only cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false); the description supplies the operational detail they lack.

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-loads the core purpose, then segments guidance with explicit labels (When to use, Prerequisites, Validation, Side effects, Returns), so an agent can scan to the relevant part. Every sentence carries information, though a few clauses duplicate the schema's per-parameter descriptions and could be trimmed without loss.

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 with no output schema, the definition covers the full calling picture: how to obtain the key, auth, validation rules, the destructive-vs-non-destructive distinction, cache purge side effects, idempotency, and the return shape ({status, message, key}). Nothing an agent needs in order to call it 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?

Schema coverage is 100%, so the baseline is 3, and the description largely synthesizes what the schema already documents per-field. It earns the extra point by consolidating the omit-vs-clear trap across fields into one readable rule and restating the http(s):// and non-empty validation constraints, which is the highest-risk mistake for a patch-style update with 11 parameters.

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 ('Updates an existing link card or header social icon on a Linq.es Link-in-Bio profile by its unique key') plus the scope of what is preserved (section placement, animation, schedule timestamps). An agent can distinguish this from add_profile_link and delete_profile_link without opening any 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?

Explicitly names when to use it (title, URLs, badge, visibility changes; active:false as a non-destructive hide) and names the alternatives with their selecting conditions ('use delete_profile_link only for permanent removal, or add_profile_link to create a new link'). It also states a prerequisite workflow: call list_profile_links first to obtain 'key' and current values.

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.