Trello MCP Server

Delete Attachment

delete_attachment

Remove an attachment from a Trello card by supplying the card ID and the attachment ID. Keep cards organized by deleting unwanted files.

Instructions

Delete an attachment from a Trello 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>",
      "attachmentId": "<attachmentId>"
    },
    "name": "delete_attachment"
  }
}

Input Schema

Name	Required	Description	Default
`cardId`	Yes	The ID of the card
`attachmentId`	Yes	The ID of the attachment to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the responsibility for disclosing behavior. While 'Delete' conveys that the operation is destructive, it does not mention permanence, irreversibility, permissions, side effects, or whether the operation can be undone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single clear sentence with no filler or redundant detail. It is front-loaded with the operative verb and resource, making the tool's purpose immediately scannable.

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

Completeness3/5

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

The tool is simple, the parameters are fully described, and no output schema exists, but the description omits important context for a destructive operation, such as whether deletion is permanent or requires specific permissions. It is minimally adequate but leaves safety-related details unstated.

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 already fully documents both parameters with descriptions ('The ID of the card', 'The ID of the attachment to delete'), so the description adds little beyond restating the card context. With 100% schema coverage, a baseline of 3 is appropriate.

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 uses a specific verb ('Delete') and identifies the exact resource ('an attachment from a Trello card'), making the tool's function immediately clear. It also differentiates from sibling tools like add_attachment and list_attachments.

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?

No guidance is given on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The intended use is only implied by the name and short description, with no explicit routing or conditional guidance.

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

Deploy Server