Skip to main content
Glama

Playbook

by com.playbook
OverviewDiscussionsAdmin

Update board

update_board
DestructiveIdempotent

Update an existing board's title, description, or parent. Pass only the fields you want to change. To rename a board, pass just title. To move it under a different parent, pass parent_collection_token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoNew title
tokenYesBoard token
descriptionNoNew description
organizationNoWorkspace slug, as returned by list_organizations. Omit it when the account has a single workspace — it is then resolved from your token. Pass it only when the account has several, or when you mean a workspace other than the obvious one.
parent_collection_tokenNoNew parent board token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "token",
-  "context"
-]New value: +[
+  "token"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description adds genuinely useful partial-update semantics (PATCH-like behavior, only supplied fields change), which the annotations don't convey. However, annotations declare destructiveHint=true and the description never mentions that reparenting or editing can be destructive or whether changes are reversible — a notable omission given the mutation profile.

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?

Three short sentences, front-loaded with the mutation scope and followed by the two most common usage patterns. Every sentence carries actionable information with no filler.

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 a mutation tool with full schema coverage, no output schema, and annotations covering idempotency and safety, the description supplies enough to call it correctly. The only gap is the absence of any warning aligned with destructiveHint=true.

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 100%, so the fields and the organization-resolution rule are already documented in the schema. The description adds intent-based mapping ('to rename, pass just title'; reparenting uses parent_collection_token'), which is modest added value over the structured data, keeping it near the baseline.

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 ('Update'), resource ('an existing board'), and the exact mutable fields (title, description, parent), which cleanly separates it from create_board and delete_board. It stops short of naming any sibling explicitly, so it lands just below the top mark.

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

Usage Guidelines4/5

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

Gives concrete operational guidance: pass only the fields you want to change, and two worked intent-to-parameter examples (rename via `title`, reparent via `parent_collection_token`). It doesn't state when not to use this tool or point to a board-specific alternative, but no such sibling exists here.

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

All Playbook toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources