Skip to main content
Glama

get-project-member-group-list

Retrieve all member groups configured in a Dooray project to assign tasks to collections of members efficiently.

Instructions

Get list of member groups in a project.

Member groups are collections of members that can be assigned to tasks as a group. This tool retrieves all member groups configured in a project.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.

Pagination:

  • Default page size is 20 (maximum: 100)

  • Use page parameter to get additional pages if totalCount > size

Note: Returns compact response with essential fields only (id and code).

Examples:

  • Get all member groups: {"projectId": "123456"}

  • Get with pagination: {"projectId": "123456", "page": 0, "size": 50}

Returns a paginated response with totalCount and array of member groups containing:

  • id: Member group ID

  • code: Member group name/code

Use this tool to find member groups for assigning tasks to groups of members.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID to get member groups from
pageNoPage number for pagination (default: 0)
sizeNoNumber of items per page (default: 20, max: 100)

Implementation Reference

  • The main execution handler for the 'get-project-member-group-list' tool. It fetches paginated member groups from the projects API, filters the data using filterMemberGroupForList, formats as compact JSON, and handles errors.
    export async function getProjectMemberGroupListHandler(args: GetProjectMemberGroupListInput) {
      try {
        const result = await projectsApi.getProjectMemberGroups({
          projectId: args.projectId,
          page: args.page,
          size: args.size,
        });
    
        // Filter to compact response to reduce token usage
        const compactResult = {
          totalCount: result.totalCount,
          data: result.data.map(filterMemberGroupForList),
        };
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(compactResult, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${formatError(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema for validating tool arguments and TypeScript type inference.
    export const getProjectMemberGroupListSchema = z.object({
      projectId: z.string().describe('Project ID to get member groups from'),
      page: z.number().optional().describe('Page number (default: 0)'),
      size: z.number().optional().describe('Items per page (default: 20, max: 100)'),
    });
    
    export type GetProjectMemberGroupListInput = z.infer<typeof getProjectMemberGroupListSchema>;
  • Tool metadata object with name, detailed description, and JSON inputSchema used for listing tools in MCP.
    export const getProjectMemberGroupListTool = {
      name: 'get-project-member-group-list',
      description: `Get list of member groups in a project.
    
    Member groups are collections of members that can be assigned to tasks as a group. This tool retrieves all member groups configured in a project.
    
    **URL Pattern Recognition**:
    When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter.
    
    **Pagination**:
    - Default page size is 20 (maximum: 100)
    - Use page parameter to get additional pages if totalCount > size
    
    **Note**: Returns compact response with essential fields only (id and code).
    
    Examples:
    - Get all member groups: {"projectId": "123456"}
    - Get with pagination: {"projectId": "123456", "page": 0, "size": 50}
    
    Returns a paginated response with totalCount and array of member groups containing:
    - **id**: Member group ID
    - **code**: Member group name/code
    
    Use this tool to find member groups for assigning tasks to groups of members.`,
      inputSchema: {
        type: 'object',
        properties: {
          projectId: {
            type: 'string',
            description: 'Project ID to get member groups from',
          },
          page: {
            type: 'number',
            description: 'Page number for pagination (default: 0)',
          },
          size: {
            type: 'number',
            description: 'Number of items per page (default: 20, max: 100)',
          },
        },
        required: ['projectId'],
      },
    };
  • src/index.ts:62-62 (registration)
    Registration of the tool handler and schema in the central toolRegistry map used for tool execution.
    'get-project-member-group-list': { handler: getProjectMemberGroupListHandler, schema: getProjectMemberGroupListSchema },
Behavior4/5

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

With no annotations provided, the description carries full burden and delivers well. It discloses pagination behavior (default page size 20, max 100, page parameter usage), URL pattern recognition for extracting projectId, and response format details (compact response with id and code only). No contradictions exist since annotations are absent.

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?

Well-structured with clear sections (description, URL pattern, pagination, note, examples, returns, usage). While comprehensive, some sections like the detailed examples and returns explanation could be slightly condensed. Every sentence adds value, but it's moderately verbose rather than maximally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with no annotations and no output schema, the description provides excellent completeness. It covers purpose, usage context, behavioral details (pagination, URL parsing, response format), parameter guidance, and examples. The agent has all necessary information to use this tool 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?

Schema description coverage is 100%, providing solid baseline documentation for all three parameters. The description adds some value with URL pattern recognition guidance for extracting projectId and pagination context, but doesn't significantly enhance parameter meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get list' and resource 'member groups in a project', with additional context about what member groups are ('collections of members that can be assigned to tasks as a group'). It distinguishes from siblings like 'get-project-member-list' by focusing specifically on groups rather than individual members.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided: 'Use this tool to find member groups for assigning tasks to groups of members.' This gives clear context for when to use this tool versus alternatives like 'get-project-member-list' for individual members or other sibling tools for different resources.

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/jhl8041/dooray-mcp'

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