Skip to main content
Glama
jhl8041

Dooray MCP Server

by jhl8041
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get-task-comment-list

Read-onlyIdempotent

Fetches paginated comments from a specific Dooray task so you can review discussion history, progress updates, and team notes. Supports sorting oldest or newest first.

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the safety profile is free; the description adds real value by disclosing that the response is filtered to essential fields only and by spelling out default page size and the 100-item cap. It omits rate limits, auth requirements, and whether all comments or only visible ones are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Purpose is front-loaded and the sectioned layout is scannable, but the Pagination and Sorting blocks duplicate the schema's enum and default/max values almost verbatim, and the three examples largely repeat the same shape. For a simple paginated list call this is longer than it needs to be.

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?

With no output schema, the description carries the return contract itself: totalCount plus id, creator (member vs emailUser shapes), and body with mimeType/content. Combined with pagination, sorting, URL parsing, and required-param emphasis, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; however the description adds genuine meaning by explaining how to derive projectId and taskId from Dooray URLs and by reinforcing that both are REQUIRED. Pagination and order details merely restate schema descriptions, so it doesn't reach 5.

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?

States a specific verb+resource ("Get list of comments (댓글) on a specific Dooray task") with scope ("all comments that have been added to a task"). The plural 'list/all comments' framing plainly separates it from the singular get-task-comment sibling.

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?

Closes with "Use this tool to view discussion history, progress updates, or notes on a task," giving clear situational context. It never states when NOT to use it or points to get-task-comment / create-task-comment as alternatives, so it stops short of explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools