Skip to main content
Glama

remove-project-member

Remove a member from a Miro project to manage team access and permissions. This tool requires organization, team, project, and member IDs for Enterprise accounts.

Instructions

Removes a member from a project (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesThe ID of the organization to which the project belongs
teamIdYesThe ID of the team to which the project belongs
projectIdYesThe ID of the project from which you want to remove a member
memberIdYesThe ID of the member that you want to remove from a project

Implementation Reference

  • The asynchronous handler function that executes the tool logic: calls MiroClient's enterpriseDeleteProjectMember API with orgId, teamId, projectId, memberId, formats the response, and handles errors.
    fn: async ({ orgId, teamId, projectId, memberId }) => {
      try {
        const response = await MiroClient.getApi().enterpriseDeleteProjectMember(
          orgId,
          teamId,
          projectId,
          memberId
        );
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error removing project member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input arguments for the tool: orgId, teamId, projectId, memberId.
    args: {
      orgId: z.string().describe("The ID of the organization to which the project belongs"),
      teamId: z.string().describe("The ID of the team to which the project belongs"),
      projectId: z.string().describe("The ID of the project from which you want to remove a member"),
      memberId: z.string().describe("The ID of the member that you want to remove from a project")
    },
  • src/index.ts:201-201 (registration)
    Registers the removeProjectMemberTool with the ToolBootstrapper.
    .register(removeProjectMemberTool)
  • src/index.ts:100-100 (registration)
    Imports the tool definition for registration.
    import removeProjectMemberTool from './tools/removeProjectMember.js';
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It states the action is a removal (implying mutation/destructive) but doesn't cover permissions needed, whether removal is reversible, side effects, or response format. For a mutation tool with zero annotation coverage, this is a significant gap.

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 with zero wasted words. It front-loads the core action and includes a necessary constraint ('Enterprise only') without redundancy, making it optimally concise.

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?

Given the tool's complexity (destructive mutation with 4 required parameters), lack of annotations, and no output schema, the description is incomplete. It fails to address behavioral traits like authorization needs, consequences of removal, or what the agent can expect upon success/failure, leaving critical gaps for safe invocation.

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 four parameters clearly documented in the schema itself. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for adequate coverage without extra value.

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 ('Removes') and target ('a member from a project'), making the purpose evident. It distinguishes from siblings like 'remove-board-member' by specifying 'project' context. However, it doesn't explicitly differentiate from other member-removal tools beyond the project scope.

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 minimal guidance with '(Enterprise only)', indicating a usage constraint, but offers no explicit when-to-use advice, alternatives (e.g., vs. 'remove-board-member'), prerequisites, or error conditions. This leaves the agent with little context for tool selection.

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