Skip to main content
Glama

get-task-list

Read-onlyIdempotent

Fetches filtered, sorted task lists from a specific Dooray project by assignee, workflow status, dates, tags, or milestones to locate relevant work items.

Instructions

Get list of tasks in a Dooray project with powerful filtering and sorting.

IMPORTANT: projectId is REQUIRED. This tool fetches tasks from a specific project.

Note: Returns compact response with essential fields only. For complete task details, use get-task.

URL Pattern Recognition: When given a Dooray URL like "https://nhnent.dooray.com/task/PROJECT_ID" or "https://nhnent.dooray.com/task/PROJECT_ID/TASK_ID", extract the PROJECT_ID (the first numeric ID after "/task/") and use it as the projectId parameter. When a URL is provided, use get-project for project info instead of get-project-list.

Member ID Filters (use organizationMemberId from get-my-member-info):

  • toMemberIds: Tasks assigned to specific members

  • ccMemberIds: Tasks where members are in CC

  • fromMemberIds: Tasks created by specific members

Workflow Filters:

  • postWorkflowClasses: ["backlog", "registered", "working", "closed"]

  • postWorkflowIds: Project-specific workflow IDs

Date Filters (flexible patterns):

  • "today" - Today's tasks

  • "thisweek" - This week's tasks

  • "prev-7d" - Last 7 days

  • "next-7d" - Next 7 days

  • ISO8601 range: "2021-01-01T00:00:00+09:00~2021-01-10T00:00:00+09:00"

Examples:

  1. All tasks in project: {"projectId": "123456"}

  2. Tasks assigned to me: {"projectId": "123456", "toMemberIds": ["my-org-member-id"]}

  3. Tasks in "working" status: {"projectId": "123456", "postWorkflowClasses": ["working"]}

  4. Tasks due today: {"projectId": "123456", "dueAt": "today"}

  5. Recent tasks (sorted by update time): {"projectId": "123456", "updatedAt": "prev-7d", "order": "-postUpdatedAt"}

  6. Tasks with specific milestone and tags: {"projectId": "123456", "milestoneIds": ["milestone123"], "tagIds": ["tag456"]}

Sorting:

  • Default: Tasks are sorted by most recently updated first (-postUpdatedAt)

  • Custom: Use order parameter with: postDueAt, postUpdatedAt, createdAt

  • Prefix with - for descending (e.g., "-createdAt")

Title search: subjects matches part of the task title only. Body and comments are not searched, so 0 results does not mean no task mentions the keyword.

Returns totalCount and tasks with id, number, subject, workflowClass, priority, milestone, tags (id only), createdAt, updatedAt. Assignees, CC and dueDate are not included: use get-task.

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": {
      "projectId": "<projectId>"
    },
    "name": "get-task-list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 0)
sizeNoItems per page (default: 20, max: 100)
dueAtNoFilter by due date (today, thisweek, prev-7d, next-7d, or ISO8601 range)
orderNoSort order: postDueAt, postUpdatedAt, createdAt (prefix with - for descending)
tagIdsNoFilter by tag IDs
subjectsNoPartial match on the task title only. Body and comments are not searched
createdAtNoFilter by creation date (today, thisweek, prev-7d, next-7d, or ISO8601 range)
projectIdYesProject ID (REQUIRED)
updatedAtNoFilter by update date (today, thisweek, prev-7d, next-7d, or ISO8601 range)
postNumberNoFilter by specific task number
ccMemberIdsNoFilter by CC member IDs
toMemberIdsNoFilter by assignee member IDs (organizationMemberId)
milestoneIdsNoFilter by milestone IDs
parentPostIdNoFilter by parent post ID (get subtasks)
fromMemberIdsNoFilter by creator member IDs
postWorkflowIdsNoFilter by workflow IDs
fromEmailAddressNoFilter by creator email address
postWorkflowClassesNoFilter by workflow classes: backlog, registered, working, closed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • changedInput schema / properties / subjects / description
      Previous value: -"Filter by task subject"New value: +"Partial match on the task title only. Body and comments are not searched"
  2. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered; the description adds the default ordering (-postUpdatedAt) and the precise set of fields returned, which matters because there is no output schema. It stops short of stating pagination defaults in the description (those live only in the schema), which keeps it from a 5.

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 purpose and the REQUIRED projectId warning are front-loaded, and headers make the long body scannable. Six worked examples plus a URL-pattern paragraph is more bulk than strictly needed, but each section carries distinct 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?

For an 18-parameter read tool with no output schema, the description supplies the missing return-value contract (field list, and the fields deliberately omitted with a pointer to get-task), the default sort, and filter syntax. An agent has everything needed to construct a correct call on the first try.

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 the baseline is 3; the description earns more by documenting the accepted date patterns, the descending-sort minus prefix, the meaning of the three member-ID families, and where to obtain member IDs. It does not cover a few parameters at all (parentPostId, postNumber, fromEmailAddress, page/size), leaving minor gaps.

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?

Opens with a specific verb + resource + scope ("list of tasks in a Dooray project with powerful filtering and sorting") and immediately distinguishes itself from get-task by noting it returns compact fields only. An agent can tell what it fetches and what it does not without reading the schema.

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 routing: use get-task for full task details, use get-project when a URL is supplied instead of get-project-list, and source organizationMemberId from get-my-member-info. It also states the negative condition that title search does not cover body or comments, so zero results are not conclusive.

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