Skip to main content
Glama

Coline

Update a board

update_board
DestructiveIdempotent

Renames a board or changes its prefix, description, default view, statuses or custom fields. Statuses and fields given replace the current lists.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
statusesNo
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
defaultViewNo
descriptionNo
taskboardIdYesBoard id from list_boards.
customFieldsNo
identifierPrefixNo

Output Schema

NameRequiredDescriptionDefault
urlYes
nameYes
taskboardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows this is a destructive but repeatable write. The description adds genuinely useful context beyond that — 'Statuses and fields given replace the current lists' warns that these lists are overwritten wholesale — but it leaves open whether omitted scalar fields (title, description) are preserved or cleared, which matters for a destructive update.

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?

Two tight sentences with the core action front-loaded and the important replacement caveat placed second. No filler; every clause carries information, though the opening 'Renames' is narrower than the list that follows it.

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

Completeness4/5

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

For an 8-parameter destructive update with an output schema present, the description supplies the crucial mutation semantics (lists are replaced). Remaining gaps are the partial-vs-full update contract and target-identification prerequisites, which are partly covered by schema field descriptions for workspace and taskboardId.

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 description coverage is only 25%, so the burden shifts to the description, and it partly meets it by mapping human terms ('renames', 'prefix') onto fields and clarifying replace-not-merge semantics for statuses and customFields. It says nothing about the nested object shape of statuses/customFields entries, the identifierPrefix letter-only constraint, or how workspace and taskboardId identify the target.

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 a concrete verb ('Renames') plus the resource ('a board') and then enumerates the mutable attributes — prefix, description, default view, statuses, custom fields. It is unambiguous which resource this touches, though it never names a sibling such as delete_board or show_board to sharpen the boundary.

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?

Usage is implied rather than stated: an agent can infer this is the tool for modifying an existing board, but there is no explicit when-to-use, no prerequisite (e.g. needing a taskboardId from list_boards), and no exclusion against alternatives. The only guidance-like sentence concerns replacement semantics, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources