Skip to main content
Glama

set_cover

Set or remove a Trello card's cover using a color or an existing image attachment.

Instructions

Set a card's cover: a colour, an existing attachment as an image, or remove the cover (remove=true).

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>"
    },
    "name": "set_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
sizeNonormal
colorNo
cardIdYes
removeNo
attachmentIdNoId of an image attachment of this card

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered structurally. The description usefully discloses that removal is possible via remove=true and that attachmentId must reference an existing image attachment of that card, but says nothing about what happens to a prior cover, side effects, or error conditions.

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?

A single front-loaded sentence with the resource, the three modes, and the removal flag. Every clause carries information and nothing is wasted.

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?

For a six-parameter mutation tool with no output schema, the description covers the modes and the required cardId context but omits the meaning of 'size' and its interaction with attachment images. It is adequate to invoke the tool in typical cases but not fully complete.

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 33%, so the description must compensate; it does add meaning for color, attachmentId (must be an existing image attachment of this card), and remove. It leaves 'size' (normal/full) completely unexplained and does not clarify that color and attachmentId are mutually exclusive modes.

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 definition names a specific verb and resource ('Set a card's cover') and enumerates the three modes it supports: colour, image attachment, or removal. No sibling in the list also manages covers, so there is nothing to disambiguate against, but the scope is unmistakable.

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

Usage Guidelines3/5

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

The description implies mode selection by listing colour, attachmentId-as-image, and remove=true, which helps an agent choose the right parameter combination. It does not state precedence when both color and attachmentId are supplied, nor any permission prerequisites for changing a cover, so guidance is implied rather than explicit.

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