Skip to main content
Glama

add-project-member

Add a user to a Miro project by specifying their email and assigning a role like owner, editor, commenter, or viewer. Requires organization, team, and project IDs.

Instructions

Adds a member to 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 to which you want to add a user
emailYesEmail ID of the user to add to the project
roleYesRole to assign to the user

Implementation Reference

  • The main handler function that executes the tool logic by calling the Miro API to add a project member.
    fn: async ({ orgId, teamId, projectId, email, role }) => {
      try {
        const addProjectMemberRequest = {
          email,
          role
        };
    
        const response = await MiroClient.getApi().enterpriseAddProjectMember(
          orgId,
          teamId,
          projectId,
          addProjectMemberRequest
        );
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error adding project member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Tool schema definition including name, description, and Zod input schema for arguments.
    const addProjectMemberTool: ToolSchema = {
      name: "add-project-member",
      description: "Adds a member to a project (Enterprise only)",
      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 to which you want to add a user"),
        email: z.string().describe("Email ID of the user to add to the project"),
        role: z.enum(["owner", "editor", "commenter", "viewer"]).describe("Role to assign to the user")
      },
  • src/index.ts:199-199 (registration)
    Registration of the add-project-member tool with the ToolBootstrapper.
    .register(addProjectMemberTool)
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. It states 'Adds a member', implying a write/mutation operation, but doesn't disclose any behavioral traits such as required permissions, whether the operation is idempotent, what happens on duplicate additions, error conditions, or rate limits. The 'Enterprise only' note is helpful but insufficient for a mutation tool with zero annotation coverage.

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 extremely concise—a single sentence with zero wasted words. It's front-loaded with the core action ('Adds a member to a project') and efficiently adds a constraint ('Enterprise only'). Every word earns its place, making it easy to parse quickly.

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 (a mutation with 5 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral nuances. While the schema covers parameters well, the description fails to provide necessary context for safe and effective use, especially for a write operation in a multi-tool environment.

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, thoroughly documenting all 5 parameters with clear descriptions and an enum for 'role'. The description adds no parameter-specific information beyond what's in the schema, not even hinting at parameter relationships (e.g., orgId/teamId/projectId hierarchy). With high schema coverage, the baseline is 3, and the description doesn't compensate with additional insights.

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 ('Adds a member') and resource ('to a project'), making the purpose immediately understandable. It also includes a useful constraint ('Enterprise only') that clarifies the scope. However, it doesn't differentiate from the sibling tool 'remove-project-member' beyond the obvious verb difference, nor does it mention other related tools like 'get-project-member' or 'update-board-member' for context.

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, only indicating it's 'Enterprise only' without explaining when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing proper permissions), when not to use it, or how it relates to sibling tools like 'remove-project-member' or 'get-project-member'. The agent must infer usage from the tool name alone.

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