Skip to main content
Glama

get-task-comment-list

Retrieve comments from a Dooray task to view discussion history, progress updates, and team notes. Supports pagination and sorting options.

Instructions

Get list of comments (댓글) on a specific Dooray task.

This tool fetches all comments that have been added to a task. Comments are discussions, updates, or notes added by team members.

URL Pattern Recognition: When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":

  • Extract the first numeric ID after "/task/" as projectId (if present)

  • Extract the second numeric ID (or the ID after "/tasks/") as taskId

IMPORTANT: Both projectId and taskId are REQUIRED.

Pagination:

  • Default page size is 20 (maximum: 100)

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

Sorting:

  • Default: createdAt (oldest comments first)

  • Use "-createdAt" to get newest comments first

Note: Returns filtered response with essential fields only (id, creator, body).

Examples:

  • Get all comments (first page): {"projectId": "123456", "taskId": "789012"}

  • Get newest comments first: {"projectId": "123456", "taskId": "789012", "order": "-createdAt"}

  • Get second page: {"projectId": "123456", "taskId": "789012", "page": 1, "size": 20}

Returns a paginated response with totalCount and array of comments containing:

  • id: Comment ID

  • creator: Who wrote the comment (member or emailUser)

    • For members: {"type": "member", "member": {"organizationMemberId": "..."}}

    • For email users: {"type": "emailUser", "emailUser": {"emailAddress": "...", "name": "..."}}

  • body: Comment content with mimeType and content

Use this tool to view discussion history, progress updates, or notes on a task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID where the task belongs
taskIdYesTask ID to get comments from
pageNoPage number (default: 0)
sizeNoItems per page (default: 20, max: 100)
orderNoSort order: createdAt (oldest first, default), -createdAt (newest first)

Implementation Reference

  • The main handler function executing the tool: fetches task comments via API, filters paginated response, stringifies and returns as text content.
    export async function getTaskCommentListHandler(args: GetTaskCommentListInput) {
      try {
        const result = await projectsApi.getTaskComments({
          projectId: args.projectId,
          taskId: args.taskId,
          page: args.page,
          size: args.size,
          order: args.order,
        });
    
        // Filter response to reduce token usage
        const filtered = filterPaginatedResponse(result, filterTaskCommentForList);
    
        return {
          content: [{ type: 'text', text: JSON.stringify(filtered, null, 2) }],
        };
      } catch (error) {
        return formatError(error);
      }
    }
  • Zod schema defining and validating the input parameters for the tool.
    export const getTaskCommentListSchema = z.object({
      projectId: z.string().describe('Project ID where the task belongs'),
      taskId: z.string().describe('Task ID to get comments from'),
      page: z.number().min(0).optional().describe('Page number (default: 0)'),
      size: z.number().min(1).max(100).optional().describe('Items per page (default: 20, max: 100)'),
      order: z.enum(['createdAt', '-createdAt']).optional().describe('Sort order: createdAt (oldest first, default), -createdAt (newest first)'),
    });
  • src/index.ts:55-55 (registration)
    Registration in the central toolRegistry mapping the tool name to its handler and schema for dynamic tool dispatch.
    'get-task-comment-list': { handler: getTaskCommentListHandler, schema: getTaskCommentListSchema },
  • src/index.ts:78-78 (registration)
    Inclusion of the tool descriptor in the tools array returned by the listTools MCP request.
    getTaskCommentListTool,
  • Tool descriptor object with name, detailed description, and input schema used for MCP tool listing and discovery.
    export const getTaskCommentListTool = {
      name: 'get-task-comment-list',
      description: `Get list of comments (댓글) on a specific Dooray task.
    
    This tool fetches all comments that have been added to a task. Comments are discussions, updates, or notes added by team members.
    
    **URL Pattern Recognition**:
    When given a Dooray task URL like "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID" or "https://nhnent.dooray.com/project/tasks/TASK_ID":
    - Extract the first numeric ID after "/task/" as projectId (if present)
    - Extract the second numeric ID (or the ID after "/tasks/") as taskId
    
    **IMPORTANT**: Both projectId and taskId are REQUIRED.
    
    **Pagination**:
    - Default page size is 20 (maximum: 100)
    - Use page parameter to get additional pages if totalCount > size
    
    **Sorting**:
    - Default: createdAt (oldest comments first)
    - Use "-createdAt" to get newest comments first
    
    **Note**: Returns filtered response with essential fields only (id, creator, body).
    
    Examples:
    - Get all comments (first page): {"projectId": "123456", "taskId": "789012"}
    - Get newest comments first: {"projectId": "123456", "taskId": "789012", "order": "-createdAt"}
    - Get second page: {"projectId": "123456", "taskId": "789012", "page": 1, "size": 20}
    
    Returns a paginated response with totalCount and array of comments containing:
    - **id**: Comment ID
    - **creator**: Who wrote the comment (member or emailUser)
      - For members: {"type": "member", "member": {"organizationMemberId": "..."}}
      - For email users: {"type": "emailUser", "emailUser": {"emailAddress": "...", "name": "..."}}
    - **body**: Comment content with mimeType and content
    
    Use this tool to view discussion history, progress updates, or notes on a task.`,
      inputSchema: {
        type: 'object',
        properties: {
          projectId: {
            type: 'string',
            description: 'Project ID where the task belongs',
          },
          taskId: {
            type: 'string',
            description: 'Task ID to get comments from',
          },
          page: {
            type: 'number',
            description: 'Page number (default: 0)',
          },
          size: {
            type: 'number',
            description: 'Items per page (default: 20, max: 100)',
          },
          order: {
            type: 'string',
            enum: ['createdAt', '-createdAt'],
            description: 'Sort order: createdAt (oldest first, default), -createdAt (newest first)',
          },
        },
        required: ['projectId', 'taskId'],
      },
    };
Behavior5/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 and does so comprehensively. It explains URL pattern recognition for extracting IDs, emphasizes that both IDs are REQUIRED, details pagination behavior (default page size, maximum, how to get additional pages), describes sorting options with defaults, and notes the filtered response format. This goes well beyond basic functionality disclosure.

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 well-structured with clear sections (URL Pattern Recognition, IMPORTANT, Pagination, Sorting, Note, Examples, Returns, Use case) and front-loads the core purpose. While comprehensive, some sections could be more concise - for example, the URL pattern explanation is quite detailed. Overall, most sentences earn their place by adding valuable information.

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?

Given the tool's complexity (5 parameters, pagination, sorting, URL parsing) and the absence of both annotations and output schema, the description provides complete context. It explains behavioral aspects, provides practical examples, documents the return structure in detail, and gives clear usage guidance. This fully compensates for the lack of structured metadata.

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 5 parameters thoroughly. The description adds some value by emphasizing that both projectId and taskId are REQUIRED (though the schema's required array already indicates this) and provides practical examples with all parameters. However, it doesn't add significant meaning beyond what the schema provides, meeting the baseline for high schema coverage.

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 tool's purpose with specific verb ('Get list of comments') and resource ('on a specific Dooray task'), distinguishing it from siblings like 'get-task' (which fetches task details) and 'create-task-comment' (which creates new comments). It explains what comments are ('discussions, updates, or notes added by team members'), providing context beyond just the name.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('to view discussion history, progress updates, or notes on a task'), but doesn't explicitly mention when NOT to use it or name specific alternatives. While it distinguishes from siblings by function, it lacks explicit guidance like 'use get-task for task details instead of comments'.

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