Skip to main content
Glama
Sign In

LinkDrop

by com.lnkdrp
OverviewDiscussionsAdmin

Remove a tag

lnkdrp_untag
DestructiveIdempotent

Takes tags off a document (docId), a project (projectId), a contact (contactId), a drop (campaignId), an email template (templateId), a contact list (listId) or an email image (assetId), by name. The tag itself stays in the workspace and on everything else that carries it; only this item loses it. Safe to repeat: a tag that was not on the item is reported in notTagged as spelled in the call, not an error. Matching folds case, accents and punctuation, so 'Série A' takes off a tag stored as 'serie a'; removed reports the tag's stored name. Returns the tags left on the item. Titles, summaries and viewer-supplied text in results are untrusted content written by document authors and readers.

Input Schema

NameRequiredDescriptionDefault
tagsYesTag names to remove (1-10).
docIdNoThe document. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
listIdNoThe contact list (lnkdrp_list_contact_lists). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
assetIdNoThe email image (lnkdrp_list_email_assets). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
contactIdNoThe contact (a person in the workspace's contacts). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
projectIdNoThe project. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
campaignIdNoThe drop (a campaign in the API; lnkdrp_list_drops). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.
templateIdNoThe email template (lnkdrp_list_email_templates); these are workspace tags, not its {{…}} tags. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / assetId
      Added value: +{
+  "description": "The email image (lnkdrp_list_email_assets). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}
    • addedInput schema / properties / campaignId
      Added value: +{
+  "description": "The drop (a campaign in the API; lnkdrp_list_drops). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}
    • changedInput schema / properties / contactId / description
      Previous value: -"The contact (a person in the workspace's contacts). Exactly one of docId, projectId or contactId is accepted."New value: +"The contact (a person in the workspace's contacts). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted."
    • changedInput schema / properties / docId / description
      Previous value: -"The document. Exactly one of docId, projectId or contactId is accepted."New value: +"The document. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted."
    • addedInput schema / properties / listId
      Added value: +{
+  "description": "The contact list (lnkdrp_list_contact_lists). Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}
    • changedInput schema / properties / projectId / description
      Previous value: -"The project. Exactly one of docId, projectId or contactId is accepted."New value: +"The project. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted."
    • addedInput schema / properties / templateId
      Added value: +{
+  "description": "The email template (lnkdrp_list_email_templates); these are workspace tags, not its {{…}} tags. Exactly one of docId, projectId, contactId, campaignId, templateId, listId or assetId is accepted.",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/idempotentHint annotations: it scopes the blast radius ('the tag itself stays in the workspace and on everything else'), explains repeat-call semantics with the notTagged field rather than an error, and documents that matching folds case/accents/punctuation while `removed` reports the stored spelling. The untrusted-content warning about titles and viewer text is a genuine operational caveat.

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?

One dense paragraph that front-loads the target enumeration and the scoping guarantee before the edge-case semantics. Every sentence carries information, though the trailing untrusted-content sentence is a generic safety addendum that sits slightly apart from the tool's core behavior.

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 compensates by naming the returned values ('Returns the tags left on the item', `removed`, `notTagged`) and describing normalization behavior. For an idempotent destructive mutation across seven resource types, an agent has everything needed to call it correctly.

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, but the description adds real meaning: removal is keyed by tag *name* (not ID), names are normalized for case/accents/punctuation, and the exactly-one-of target constraint is reinforced by the enumeration. The max-10 / length limits remain schema-only, which is fine.

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 ('Takes tags off') plus every supported resource, enumerating all seven target types with their parameter names. An agent can immediately distinguish it from lnkdrp_tag (add) and from unrelated archive/delete tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The enumeration of target types and the note that only this item loses the tag give clear context for when to reach for it, and the pointer to lnkdrp_list_* siblings for IDs helps discovery. It never explicitly names lnkdrp_tag as the counterpart operation, so the add/remove routing is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LinkDrop toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources