Skip to main content
Glama

add_attachment

Attach a URL link to a Trello card by providing its card ID and the URL.

Instructions

Attach a URL (link) to a card.

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": {
      "cardId": "<cardId>",
      "url": "<url>"
    },
    "name": "add_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameNo
cardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this is a non-destructive mutation with openWorldHint=true. The description adds that the attachment is a URL rather than an uploaded file, which is genuinely useful context. However, it leaves open whether the server fetches the URL, how it behaves if the URL is unreachable, and whether duplicate links are allowed.

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 a single, front-loaded sentence with no filler, so it is easy to parse at a glance. Its weakness lies in under-specification, not conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a 4-parameter mutation tool with 25% schema coverage, no output schema, and openWorldHint=true, so the description needs to carry a lot of context but does not. It never explains the name parameter, the lang requirement, or what happens on the server side when the URL is attached.

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?

Schema coverage is only 25%: only the lang parameter is documented (ISO 639-1), while name and cardId have no descriptions. The description covers url and cardId implicitly but says nothing about the name parameter (display label?) or lang, so it does not compensate for the coverage gap. Baseline 3 applies because the schema covers the essential required parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("Attach a URL (link) to a card"), nicely distinguishing this from add_comment, add_checklist_item, and add_label, which each create different card artifacts. It does not, however, contrast itself with siblings that also accept URLs (e.g. set_cover), so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives. The only hint is the implied usage of the name itself (linking a URL to a card) and the parenthetical "(link)", which signals URL attachments rather than file uploads.

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