Plane MCP Server

retrieve_work_item_activity

Retrieve a specific work item activity by providing the project ID, work item ID, and activity ID. Returns the activity object for detailed review.

Instructions

Retrieve a specific activity for a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item activity_id: UUID of the activity

Returns: WorkItemActivity object

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>",
      "activity_id": "<activity_id>"
    },
    "name": "retrieve_work_item_activity"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`activity_id`	Yes
`work_item_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`verb`	No
`actor`	No
`epoch`	No
`field`	No
`issue`	No
`comment`	No
`project`	Yes
`new_value`	No
`old_value`	No
`workspace`	Yes
`created_at`	No
`deleted_at`	No
`updated_at`	No
`attachments`	No
`issue_comment`	No
`new_identifier`	No
`old_identifier`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. 'Retrieve' implicitly indicates a read-only operation, and it states the return type, but it does not mention potential errors, permission requirements, or absence of side effects. This is adequate for a simple read operation but lacks richer context.

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 concise and well-structured with an Args/Returns format. Every line provides necessary information—the action, each parameter's purpose, and the return type—without any redundant wording.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the core aspects: what it does, all required parameters, and the return type. It does not discuss error handling or permission prerequisites, but for a straightforward retrieve operation this is mostly sufficient. A brief note distinguishing it from list_work_item_activities would improve completeness.

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?

The description adds meaningful context beyond the schema by specifying that each parameter is a UUID for its respective resource. While the schema only lists property names and types as strings, the description clarifies the exact semantic role and format, which is valuable for correct invocation.

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 the tool retrieves a specific activity for a work item, using the verb 'retrieve' and specifying the resource. It distinguishes itself from the sibling 'list_work_item_activities' by focusing on a single activity, and the required activity_id parameter reinforces this.

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 explicit guidance is given about when to use this tool versus alternatives like list_work_item_activities. The word 'specific' implies it is for fetching by ID, but there is no direct comparison or exclusion, leaving the agent without clear decision criteria.

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

Deploy Server