Plane MCP Server

list_work_item_activities

List all activities for a specific work item by providing project and work item IDs. Retrieve a detailed history of updates, comments, and changes for tracking work item progress.

Instructions

List activities for a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item params: Optional query parameters as a dictionary

Returns: List of WorkItemActivity objects

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": {
      "project_id": "<project_id>",
      "work_item_id": "<work_item_id>"
    },
    "name": "list_work_item_activities"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No
`project_id`	Yes
`work_item_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the return type ('List of WorkItemActivity objects') and the optional 'params' dictionary, but does not mention pagination, permissions, or any side effects. For a read-only list operation, this is acceptable but not richly detailed.

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 compact docstring with clearly labeled Args and Returns sections. Every sentence adds value and there is no fluff or redundant information.

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

Completeness4/5

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

For a simple list tool with an output schema, the description covers purpose, parameters, and return type adequately. It lacks explicit usage guidance and deeper parameter details, but the presence of the output schema reduces the need to explain return structures in depth.

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?

With 0% schema description coverage, the description compensates by explaining each parameter: 'UUID of the project', 'UUID of the work item', and 'Optional query parameters as a dictionary'. This adds real meaning beyond the schema's bare 'string' and 'object' types, though it could specify allowed query parameters.

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 'List activities for a work item' with a specific verb and resource. It distinguishes itself from the sibling 'retrieve_work_item_activity' by indicating a list operation rather than a single retrieval.

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

Usage Guidelines3/5

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

Usage is implied by the description and tool name: if a list of activities for a work item is needed, this tool is appropriate. However, there is no explicit guidance on when to use this vs. alternatives like 'retrieve_work_item_activity', nor any exclusions or prerequisites mentioned.

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

Deploy Server