Skip to main content
Glama

update_board

Rename a Trello board, edit its description, or close and reopen it to keep board details and status current.

Instructions

Rename a board, change its description, or close (archive) / reopen it.

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": {
      "boardId": "<boardId>"
    },
    "name": "update_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo
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
closedNo
boardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/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 safety profile is largely covered. The description adds real value by equating 'close' with 'archive', telling the agent the operation is a reversible state change rather than deletion. It does not say what happens to a closed board's lists/cards, whether it disappears from list_boards, or what permissions are needed.

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 that names every supported operation with zero boilerplate. Nothing is redundant and no sentence fails to earn its place.

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 5-parameter mutation tool with no output schema, the definition covers the operations but not the operational contract: partial-update semantics, permission requirements, and the effect of archiving are all unstated. Annotations cover the read/write safety classification, so this is adequate but with clear gaps.

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 20% (only 'lang' is documented), so the description has to carry weight — and it does partially, mapping 'rename' to name, 'change its description' to desc, and 'close/reopen' to the closed boolean. It says nothing about boardId (the sole required field), about whether omitted fields are left unchanged (partial vs full update), or about value constraints on name/desc.

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 uses specific verbs against a specific resource: rename, change description, close/reopen a board. It also disambiguates 'close' as archive, which the sibling name delete_board alone would not resolve. It does not explicitly rule out create_board/copy_board/delete_board, but the enumerated operations make the boundary clear enough.

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, and no alternative is named. The agent must infer from the verb list that this is the only tool for renaming or archiving a board, rather than being told so. Prerequisites (existing board, membership rights) are absent.

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