livediagram

Change a Plan board

change_board

Change a board’s title, its columns (every column by name, left to right: names it has keep their cards, new names are new columns) or the card types it shows and takes. A card shows on a board only when the board takes its card type.

Input Schema

TableJSON Schema

Name	Required	Description
`board`	Yes	The board, by its title, or its id when two share a title (list_items lists them).
`title`	No	A new title.
`types`	No	The card types it shows and takes, by name; "every type" shows every type again, and an empty list takes none (no card shows on it).
`columns`	No	Every column, by name, left to right. A name the board has keeps its column and cards; a name other boards use shares their column; any other name is a new, empty column. A column left out leaves its cards off this board.
`cardSize`	No	How much of each card it draws: minimal (one line), compact (a title over one row), detailed (every field, the title on up to three lines).
`swimlanes`	No	Its rows: none, assignee, type, priority, status, or a field by name ("Severity", "Role"): a row per value, across every column.
`cardFields`	No	The built-in fields its cards show, by name, whole: Number, Type, Assignee, Priority, Labels, Estimate, Start Date, Due Date, Votes, Checklist, Comments, Description. A built-in field shows on a card only when both this list and the card type’s display have it; custom fields follow the type’s display alone.
`documentId`	Yes	The document (from find_documents).
`doneColumn`	No	The column whose cards count as done (Completion, and the Done phase charts read), by name; null for none.
`renameColumns`	No	Columns renamed in place, old name to new ({"To Do": "Backlog"}): each keeps its cards, WIP limit and colour. Applied before columns, which can then use the new names.

Output Schema

TableJSON Schema

Name	Required	Description
`rev`	Yes	The tab revision after it.
`url`	Yes	Link that opens the document in the livediagram editor.
`tabId`	Yes	The tab it is on.
`takes`	Yes	The card types it shows now.
`title`	Yes	The board’s title.
`columns`	Yes	Its columns now, left to right.
`cardSize`	Yes	How much of each card it draws.
`elementId`	Yes	The board element id.
`cardFields`	Yes	The built-in fields its cards show, by name.
`changesetId`	Yes	The changeset that changed it (revertible).

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 14, 2026

addedInput schema / properties / cardFields

Added value: +{
+  "description": "The built-in fields its cards show, by name, whole: Number, Type, Assignee, Priority, Labels, Estimate, Start Date, Due Date, Votes, Checklist, Comments, Description. A built-in field shows on a card only when both this list and the card type’s display have it; custom fields follow the type’s display alone.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / cardSize

Added value: +{
+  "description": "How much of each card it draws: minimal (one line), compact (a title over one row), detailed (every field, the title on up to three lines).",
+  "enum": [
+    "minimal",
+    "compact",
+    "detailed"
+  ],
+  "type": "string"
+}

addedInput schema / properties / doneColumn

Added value: +{
+  "description": "The column whose cards count as done (Completion, and the Done phase charts read), by name; null for none.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedInput schema / properties / renameColumns

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Columns renamed in place, old name to new ({\"To Do\": \"Backlog\"}): each keeps its cards, WIP limit and colour. Applied before columns, which can then use the new names.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / swimlanes

Added value: +{
+  "description": "Its rows: none, assignee, type, priority, status, or a field by name (\"Severity\", \"Role\"): a row per value, across every column.",
+  "type": "string"
+}

addedOutput schema / properties / cardFields

Added value: +{
+  "description": "The built-in fields its cards show, by name.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / cardSize

Added value: +{
+  "description": "How much of each card it draws.",
+  "enum": [
+    "minimal",
+    "compact",
+    "detailed"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "tabId",
-  "elementId",
-  "title",
-  "columns",
-  "takes",
-  "changesetId",
-  "rev",
-  "url"
-]New value: +[
+  "tabId",
+  "elementId",
+  "title",
+  "columns",
+  "takes",
+  "cardSize",
+  "cardFields",
+  "changesetId",
+  "rev",
+  "url"
+]

Changed4 schema fields changedOct 10, 2026

addedInput schema / properties / types / anyOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "const": "every type",
+    "type": "string"
+  }
+]

changedInput schema / properties / types / description

Previous value: -"The card types it shows and takes, by name; an empty list shows every type."New value: +"The card types it shows and takes, by name; \"every type\" shows every type again, and an empty list takes none (no card shows on it)."

removedInput schema / properties / types / items
```
Removed value: -{
-  "type": "string"
-}
```
removedInput schema / properties / types / type
```
Removed value: -"array"
```

AddedOct 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations declare it is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds useful semantics (existing column names keep their cards, omitted columns lose their cards from the board), but does not cover permissions, reversibility, or failure behavior beyond that.

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 that front-load the mutable fields, with the column rule and card-type rule packed into parentheticals. Efficient, though the second sentence is somewhat abstract.

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?

With annotations, a rich 100%-covered schema, and an output schema present, the description only needs to orient the agent. It does so adequately, though it could note the relationship to change_card_types given the semantic overlap.

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 100%, so the schema itself documents all 10 parameters thoroughly. The description only gestures at title, columns, and types, and never mentions cardSize, swimlanes, cardFields, doneColumn, or renameColumns. This is baseline territory given a complete schema.

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?

States a specific verb (change) and resource (a Plan board) and enumerates what can change: title, columns, card types. An agent can distinguish it from add_board, but the overlap with change_card_types (also about card types) is not addressed.

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 statement of when to use this versus siblings like change_card_types or add_board, and no prerequisites or exclusions. The 'card types it shows and takes' phrasing actually overlaps with change_card_types without clarifying the boundary.

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

All livediagram tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?