Skip to main content
Glama
Sign In
ClickUp MCP Server

ClickUp MCP Server

by ttttdiva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task_comments

Fetch a task's comment list by providing its task ID, enabling quick review of all associated discussions.

Instructions

タスクのコメント一覧を取得します。

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesタスクID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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. It only says 'retrieves comment list' but does not mention pagination, ordering, permission requirements, or the structure of returned comments. This is minimal disclosure for a read operation.

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

Conciseness5/5

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

The description is a single concise sentence that immediately conveys the purpose with no filler. It is appropriately structured for a simple tool.

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

Completeness2/5

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

With no output schema and no annotations, the description is thin. It does not explain the return format, fields, or any behavioral caveats beyond 'list'. For a tool with one parameter, it is minimally viable but lacks important context for an agent to fully understand the tool's behavior.

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?

The input schema fully describes task_id as 'タスクID' with 100% coverage. The description implies task context but adds no meaning beyond the schema. Baseline 3 applies because the schema handles parameter semantics.

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 it retrieves the list of comments for a task, using a specific verb ('取得' - retrieve) and resource ('コメント一覧' - comment list). This distinguishes it from sibling tools like add_comment (which adds) and get_task_detail (which gets task information).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_task_detail or add_comment. The description simply states what the tool does without context, prerequisites, or exclusions.

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