Skip to main content
Glama

remove-board-member

Remove a specific member from a Miro board by providing the board ID and member ID to manage board access and permissions.

Instructions

Remove a specific member from a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board
memberIdYesID of the board member to remove

Implementation Reference

  • The asynchronous handler function that implements the core logic for the 'remove-board-member' tool. It validates inputs, calls the MiroClient API to remove the board member, and handles errors with ServerResponse.
    fn: async ({ boardId, memberId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!memberId) {
          return ServerResponse.error("Member ID is required");
        }
    
        const result = await MiroClient.getApi().removeBoardMember(boardId, memberId);
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error removing board member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including name, description, and Zod input schema for the 'remove-board-member' tool.
    const removeBoardMemberTool: ToolSchema = {
      name: "remove-board-member",
      description: "Remove a specific member from a Miro board",
      args: {
        boardId: z.string().describe("ID of the board"),
        memberId: z.string().describe("ID of the board member to remove")
      },
  • src/index.ts:175-175 (registration)
    The registration of the 'removeBoardMemberTool' in the ToolBootstrapper chain in the main index file.
    .register(removeBoardMemberTool)
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. While 'Remove' implies a destructive mutation, the description doesn't specify whether this action is reversible, what permissions are required, whether it affects board access, or what happens to the member's content. It lacks critical behavioral context for a destructive operation.

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 states exactly what the tool does with zero wasted words. It's appropriately sized and front-loaded with the core functionality.

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 destructive mutation tool with no annotations and no output schema, the description is insufficient. It doesn't address behavioral aspects like permission requirements, consequences of removal, or what the tool returns. Given the complexity of removing a board member, more context about the operation's impact is needed.

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?

The input schema has 100% description coverage with clear parameter documentation, so the baseline is 3. The description doesn't add any parameter-specific information beyond what's already in the schema (boardId and memberId are self-explanatory), but it doesn't need to since the schema is comprehensive.

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 ('Remove') and target ('a specific member from a Miro board'), providing a specific verb+resource combination. It doesn't explicitly differentiate from sibling tools like 'remove-project-member', but the distinction is implied through the resource specificity (board member vs project member).

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. There's no mention of prerequisites (e.g., needing board admin permissions), when not to use it, or how it differs from similar tools like 'update-board-member' or 'remove-project-member' in the sibling list.

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