Skip to main content
Glama

get-project-member

Retrieve specific member information from Miro projects to manage team access and permissions within enterprise organizations.

Instructions

Retrieves information about a specific project member (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 retrieve specific member information
memberIdYesThe ID of the member for which you want to retrieve information

Implementation Reference

  • The core handler function for the 'get-project-member' tool. It calls the MiroClient API to fetch project member details using provided IDs and returns the JSON response or an error.
    fn: async ({ orgId, teamId, projectId, memberId }) => {
      try {
        const response = await MiroClient.getApi().enterpriseGetProjectMember(
          orgId,
          teamId,
          projectId,
          memberId
        );
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving project member: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including name, description, and Zod schemas for input parameters (orgId, teamId, projectId, memberId).
    const getProjectMemberTool: ToolSchema = {
      name: "get-project-member",
      description: "Retrieves information about a specific project member (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 from which you want to retrieve specific member information"),
        memberId: z.string().describe("The ID of the member for which you want to retrieve information")
      },
  • src/index.ts:200-200 (registration)
    Registration of the getProjectMemberTool with the ToolBootstrapper instance in the main index file.
    .register(getProjectMemberTool)
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 'retrieves' implies a read-only operation, it doesn't specify authentication requirements, rate limits, error conditions, or what information is actually returned. The 'Enterprise only' note is helpful but insufficient for a tool with no 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose upfront. The 'Enterprise only' qualification is appropriately placed. There's no wasted verbiage, though it could be slightly more informative while maintaining conciseness.

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 tool with 4 required parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what information is retrieved, the format of the response, error handling, or how this differs from similar member retrieval tools. The 'Enterprise only' note is the only contextual information provided.

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 all parameters are documented in the schema. The description adds no additional parameter information beyond what's already in the schema descriptions. This meets the baseline expectation when schema does the heavy lifting, but adds no 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 verb ('retrieves information') and resource ('about a specific project member'), making the purpose unambiguous. It distinguishes from sibling tools like 'get-organization-member' by specifying the project context. However, it doesn't explicitly differentiate from 'get-specific-board-member' which might retrieve similar information at board level.

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 noting this is 'Enterprise only' without explaining when to use this tool versus alternatives like 'get-organization-member' or 'get-specific-board-member'. No context about prerequisites, when this tool is appropriate, or what distinguishes it from similar retrieval tools is provided.

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