Skip to main content
Glama

Linq.es MCP Server

Delete Profile Link

delete_profile_link
DestructiveIdempotent

Permanently deletes a link card or header social icon from a Linq.es Link-in-Bio profile by its unique 'key'. When to use: use only when the user explicitly wants permanent removal; prefer update_profile_link with active: false to temporarily hide a link while preserving its click history. Prerequisites: requires Bearer lnq_live_ Pro authentication; call list_profile_links first to look up and confirm the exact 'key' belonging to the user. Validation: 'key' must be non-empty and belong to the authenticated user; if the key is missing, already deleted, or owned by another user, returns isError: true ('Link not found or access denied.'). Side effects: destructive and irreversible (deletes the link document from Firestore and immediately purges in-memory, HTML, and CDN caches for the owning profile). 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>"
    },
    "name": "delete_profile_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesUnique Firestore document key of the link to permanently delete, obtained from list_profile_links.

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 destructiveHint=true and idempotentHint=true, and the description adds substantial context beyond them: irreversibility, Firestore document deletion, cache purges (in-memory, HTML, CDN), Bearer lnq_live_<key> Pro auth, and the isError behavior on missing/foreign keys.

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?

Dense but organized with labeled sections (When to use, Prerequisites, Validation, Side effects, Returns), making it easy to scan. It is slightly long, but nearly every clause carries actionable information.

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?

With no output schema, the description supplies the return shape ({status, message, key}), error behavior, auth requirements, and destructive side effects. Nothing an agent needs to invoke it safely 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 schema documents the single key parameter. The description adds validation semantics beyond the schema: that the key must be non-empty, belong to the authenticated user, and be obtained from list_profile_links, plus the error message for invalid keys.

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 (permanently deletes), a precise resource (link card or header social icon from a Linq.es Link-in-Bio profile) and the identifier (key). This clearly separates it from siblings like update_profile_link and add_profile_link.

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 use it (only when the user wants permanent removal) and names the alternative (update_profile_link with active: false to hide while preserving click history). It also gives the prerequisite of calling list_profile_links first to confirm the key.

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