Skip to main content
Glama

get-organization-members

Retrieve organization member lists with filtering options for roles, licenses, and status to manage team access and permissions in Miro.

Instructions

Retrieves a list of members for an organization (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesid of the organization
emailsNoFilter by comma-separated email addresses
roleNoFilter by user role
licenseNoFilter by license type
activeNoFilter by active status
cursorNoCursor for pagination
limitNoMaximum number of results to return

Implementation Reference

  • The handler function that implements the tool logic: constructs query parameters from inputs and calls the Miro API to get organization members.
    fn: async ({ orgId, emails, role, license, active, cursor, limit }) => {
      try {
        const query: any = {};
        if (emails) query.emails = emails;
        if (role) query.role = role;
        if (license) query.license = license;
        if (active !== undefined) query.active = active;
        if (cursor) query.cursor = cursor;
        if (limit) query.limit = limit;
    
        const response = await MiroClient.getApi().enterpriseGetOrganizationMembers(orgId, query);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving organization members: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Input schema using Zod for validating tool parameters like orgId, filters, and pagination.
    args: {
      orgId: z.string().describe("id of the organization"),
      emails: z.string().optional().nullish().describe("Filter by comma-separated email addresses"),
      role: z.enum(['organization_internal_admin', 'organization_internal_user', 'organization_external_user', 'organization_team_guest_user', 'unknown']).optional().nullish().describe("Filter by user role"),
      license: z.enum(['full', 'occasional', 'free', 'free_restricted', 'full_trial', 'unknown']).optional().nullish().describe("Filter by license type"),
      active: z.boolean().optional().nullish().describe("Filter by active status"),
      cursor: z.string().optional().nullish().describe("Cursor for pagination"),
      limit: z.number().optional().nullish().describe("Maximum number of results to return")
    },
  • src/index.ts:197-197 (registration)
    Registers the getOrganizationMembersTool with the ToolBootstrapper instance.
    .register(getOrganizationMembersTool)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Enterprise only' indicating access restrictions, but fails to describe key behaviors: whether this is a read-only operation, if it requires specific permissions, pagination details (implied by 'cursor' parameter but not explained), rate limits, or what the returned list structure looks like. For a tool with 7 parameters and no annotations, this leaves significant 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 states the core purpose upfront with no wasted words. It's appropriately sized for a list-retrieval tool, though the lack of additional context means it may be too brief rather than verbose.

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 complexity (7 parameters, no output schema, no annotations), the description is insufficient. It doesn't explain the return format, pagination behavior, error conditions, or access requirements beyond 'Enterprise only'. For a tool that likely returns structured member data with filtering and pagination, more context is needed to help the agent use it effectively.

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 schema has 100% description coverage, thoroughly documenting all 7 parameters including 'orgId' (required), filtering options ('emails', 'role', 'license', 'active'), and pagination controls ('cursor', 'limit'). The description adds no parameter-specific information beyond what's already in the schema, meeting the baseline score when schema coverage is complete.

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 ('Retrieves a list') and resource ('members for an organization'), making the purpose evident. It also specifies 'Enterprise only' as a scope limitation. However, it doesn't differentiate from sibling tools like 'get-organization-member' (singular) or 'get-all-board-members', leaving some ambiguity about when to choose this specific tool.

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' hinting at access restrictions, but it lacks explicit when-to-use instructions. It doesn't mention alternatives (e.g., 'get-organization-member' for single members) or prerequisites, leaving the agent to infer usage from context without clear direction.

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