get-task
Retrieve complete details for a specific Dooray task by task ID or URL, including body, workflow status, assignees, attachments, and metadata; optionally omit body content.
Instructions
Get detailed information about a specific task.
This tool retrieves complete details of a task including its full body content, attachments, workflow status, assignees, and all metadata.
URL Pattern Recognition - Two formats supported:
Project-scoped URL: "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID"
Extract the first numeric ID after "/task/" as projectId (optional)
Extract the second numeric ID as taskId (required)
Example: "https://nhnent.dooray.com/task/1769381697328002548/4206132384174602537" → {"taskId": "4206132384174602537", "projectId": "1769381697328002548"}
Task-only URL: "https://nhnent.dooray.com/project/tasks/TASK_ID"
Extract the numeric ID after "/tasks/" as taskId
Example: "https://nhnent.dooray.com/project/tasks/4206132384174602537" → {"taskId": "4206132384174602537"}
Same for "https://nhnent.dooray.com/task/to/TASK_ID"
Draft URLs ("/task/write/draft/DRAFT_ID") cannot be read through the API. get-task returns 404 for them
IMPORTANT:
taskId is REQUIRED, projectId is OPTIONAL
The taskId is the unique identifier (ID) from the URL, NOT the sequential task number shown in the UI
You can fetch task details with just the taskId without knowing the projectId
When a specific task URL is provided, use this tool directly instead of calling get-project-list first
To find taskId from task descriptions, use get-task-list to search and get task IDs
Bodies can exceed 50,000 characters. When you only need status, assignees, number or dates, set includeBody to false
Examples:
From URL pattern 1: {"taskId": "4206132384174602537", "projectId": "1769381697328002548"}
From URL pattern 2: {"taskId": "4206132384174602537"}
Just taskId: {"taskId": "789012345"}
With both IDs: {"taskId": "789012345", "projectId": "123456"}
Without body: {"taskId": "789012345", "includeBody": false}
Returns complete task information including:
Basic info: id, number, subject, taskNumber (PROJECT-CODE/NUMBER format)
Project: project object with id and code
Status: workflowClass (registered/working/closed), workflow (id and name), closed flag, priority
Dates: createdAt, updatedAt, dueDate, dueDateFlag
Content: body with mimeType (text/x-markdown or text/html) and content. With includeBody false: mimeType and contentLength
Hierarchy: parent task information (id, number, subject) if this is a subtask
People: users object with from (creator), to (assignees), cc (watchers)
Organization: milestone (id, name), tags array (id only, use get-tag for names)
Files: fileIdList (attachment IDs, use get-attachment-list for names and sizes)
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"taskId": "<taskId>"
},
"name": "get-task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| taskId | Yes | Task ID (unique identifier, REQUIRED) | |
| projectId | No | Project ID (optional, can be omitted) | |
| includeBody | No | Default true. Set to false to get body mimeType and contentLength instead of the full content |