Skip to main content
Glama

update-board

Modify an existing Miro board by updating its name, description, sharing policy, or team assignment using the board ID.

Instructions

Update an existing Miro board with new settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that you want to update
nameNoNew name for the board
descriptionNoNew description for the board
sharingPolicyNoNew sharing policy for the board
teamIdNoNew team ID to assign the board to

Implementation Reference

  • The main handler function for the 'update-board' tool. It checks for required boardId, builds the changes object from optional params, calls MiroClient to update the board, and returns the result or error response.
    fn: async ({ boardId, name, description, sharingPolicy, teamId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const boardChanges = {};
        if (name) boardChanges['name'] = name;
        if (description !== undefined) boardChanges['description'] = description;
        if (sharingPolicy) boardChanges['sharingPolicy'] = { access: sharingPolicy };
        if (teamId) boardChanges['teamId'] = teamId;
    
        const boardData = await MiroClient.getApi().updateBoard(boardId, boardChanges);
    
        return ServerResponse.text(JSON.stringify(boardData, null, 2));
      } catch (error) {
        process.stderr.write(`Error updating Miro board: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod-based input schema defining parameters for updating a board: required boardId, optional name, description, sharingPolicy, and teamId.
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board that you want to update"),
      name: z.string().optional().nullish().describe("New name for the board"),
      description: z.string().optional().nullish().describe("New description for the board"),
      sharingPolicy: z.enum(['private', 'view', 'comment', 'edit']).optional().nullish().describe("New sharing policy for the board"),
      teamId: z.string().optional().nullish().describe("New team ID to assign the board to")
    },
  • src/index.ts:113-113 (registration)
    Registers the updateBoardTool (imported from './tools/updateBoard.js') with the ToolBootstrapper in the main index file.
    .register(updateBoardTool)
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Update' implies mutation, it doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or what happens to unspecified settings. The description mentions 'new settings' but doesn't elaborate on scope or constraints beyond the basic action.

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?

The description is a single, efficient sentence that gets straight to the point with zero waste. It's appropriately sized for a straightforward update operation and front-loads the core action and resource.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't address what 'new settings' encompasses, potential side effects, error conditions, or return values. Given the complexity of updating a board with multiple parameters and many sibling update tools, more context is needed for effective use.

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 schema already documents all 5 parameters thoroughly. The description adds no additional meaning about parameters beyond implying 'settings' in general. With high schema coverage, the baseline is 3 even without param-specific details in the description.

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 clearly states the action ('Update') and resource ('an existing Miro board'), making the purpose immediately understandable. It distinguishes from creation tools like 'create-board' by specifying 'existing', but doesn't explicitly differentiate from other update tools like 'update-board-classification' or 'update-board-member' among the siblings.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling update tools (e.g., update-board-classification, update-board-member), there's no indication of which settings this tool handles or when to choose it over other board-update tools. No prerequisites or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-jarzyna/mcp-miro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server