Skip to main content
Glama

update-board-member

Modify a board member's role or status on a Miro board to manage team permissions and access levels.

Instructions

Update a specific member's role or status on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board
memberIdYesID of the board member to update
roleNoNew role for the board member
statusNoNew status for the board member

Implementation Reference

  • Handler function that validates inputs, constructs changes object, calls MiroClient to update board member, and returns the result or error.
    fn: async ({ boardId, memberId, role, status }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!memberId) {
          return ServerResponse.error("Member ID is required");
        }
    
        if (!role && !status) {
          return ServerResponse.error("At least one of role or status must be provided");
        }
    
        const memberChanges: any = {};
        if (role) memberChanges.role = role;
        if (status) memberChanges.status = status;
    
        const result = await MiroClient.getApi().updateBoardMember(boardId, memberId, memberChanges);
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error updating board member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining input parameters for the update-board-member tool: boardId (required string), memberId (required string), role (optional enum), status (optional enum).
    args: {
      boardId: z.string().describe("ID of the board"),
      memberId: z.string().describe("ID of the board member to update"),
      role: z.enum(['member', 'admin', 'owner']).optional().nullish().describe("New role for the board member"),
      status: z.enum(['active', 'pending', 'blocked']).optional().nullish().describe("New status for the board member")
    },
  • src/index.ts:177-177 (registration)
    Registers the updateBoardMemberTool with the ToolBootstrapper in the main index file.
    .register(updateBoardMemberTool)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation, implying mutation, but doesn't mention required permissions, whether changes are reversible, rate limits, or what happens if only role or status is provided. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 clearly states the tool's purpose. Every word earns its place with no redundancy or unnecessary elaboration. It's appropriately sized for a straightforward update operation.

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 incomplete. It doesn't address behavioral aspects like permissions, side effects, or response format. While the schema covers parameters well, the overall context for safe and effective use is lacking given the tool's complexity as a member management operation.

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%, with all parameters well-documented in the schema itself. The description mentions 'role or status' which aligns with two parameters, but doesn't add meaningful context beyond what the schema already provides about boardId and memberId. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 verb 'update' and the resource 'specific member's role or status on a Miro board'. It distinguishes from siblings like 'add-project-member' or 'remove-board-member' by focusing on modification rather than addition or removal. However, it doesn't explicitly contrast with 'get-specific-board-member' or other update tools, keeping it at 4 rather than 5.

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. It doesn't mention prerequisites like needing admin permissions, nor does it differentiate from similar tools like 'update-board' or 'update-project-member'. Without any usage context, the agent must infer when this tool is appropriate.

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