Skip to main content
Glama
aliyun

AlibabaCloud DevOps MCP Server

Official
by aliyun

list_organization_members

Retrieve user members within an Alibaba Cloud DevOps organization by providing the organization ID, with optional pagination support for managing team access and permissions.

Instructions

list user members in an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organizationIdYesOrganization ID
pageNoPage number
perPageNoPage size

Implementation Reference

  • Tool handler that parses arguments with GetOrganizationMembersSchema, invokes the helper function getOrganizationMembersFunc, and formats the response as JSON text.
    case "list_organization_members": {
      const args = types.GetOrganizationMembersSchema.parse(request.params.arguments);
      const orgMembers = await members.getOrganizationMembersFunc(
        args.organizationId,
        args.page ?? 1,
        args.perPage ?? 100
      );
      return {
        content: [{ type: "text", text: JSON.stringify(orgMembers, null, 2)}]
      }
    }
  • Zod schema defining the input parameters for the list_organization_members tool: organizationId (required), page and perPage (optional).
    export const GetOrganizationMembersSchema = z.object({
      organizationId: z.string().describe("Organization ID"),
      page: z.number().int().optional().describe("Page number"),
      perPage: z.number().int().optional().describe("Page size"),
    });
  • Tool registration entry defining the name, description, and input schema for list_organization_members.
    {
      name: "list_organization_members",
      description: "list user members in an organization",
      inputSchema: zodToJsonSchema(types.GetOrganizationMembersSchema),
    },
  • Core helper function that builds the API endpoint URL, performs a GET request via yunxiaoRequest to fetch organization members, and validates the response using OrganizationMembersSchema.
    export const getOrganizationMembersFunc = async (
      organizationId: string,
      page: number = 1,
      perPage: number = 100
    ): Promise<OrganizationMembers> => {
    
      const url = `/oapi/v1/platform/organizations/${organizationId}/members`;
    
      const params = {
        page: page,
        perPage: perPage
      };
      const urlWithParams = buildUrl(url, params);
    
      const response = await yunxiaoRequest(urlWithParams, {
        method: "GET",
      });
    
      // 验证响应数据结构
      return OrganizationMembersSchema.parse(response);
    };
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 states the tool lists members but doesn't mention pagination behavior (implied by parameters), authentication needs, rate limits, or what the output looks like. For a read operation with pagination, this leaves significant gaps in understanding how the tool behaves.

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's front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by conveying essential information.

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 pagination parameters and no output schema, the description is incomplete. It doesn't explain the paginated nature of the listing, what the return structure looks like, or how to handle multiple pages. With no annotations and missing output details, it leaves too much undefined for effective agent use.

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 the schema already documents all three parameters (organizationId, page, perPage). The description doesn't add any meaning beyond what the schema provides—it doesn't explain parameter relationships or usage nuances. Baseline 3 is appropriate when the schema does the heavy lifting.

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 'list user members in an organization' clearly states the verb ('list') and resource ('user members in an organization'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'search_organization_members' or 'get_organization_member_info', but the core function is unambiguous.

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 like 'search_organization_members' or 'get_organization_member_info'. It also doesn't mention prerequisites, such as requiring an organization ID, which is implied by the schema but not stated in the description itself.

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/aliyun/alibabacloud-devops-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server