Plane MCP Server

create_work_log

Add a work log entry to a Plane work item by providing project ID, work item ID, duration, and description to track time spent.

Instructions

Create a work log for a work item.

Args: project_id: UUID of the project work_item_id: UUID of the work item duration: Duration of work in minutes description: Description of the work performed

Returns: Created WorkItemWorkLog 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>"
    },
    "name": "create_work_log"
  }
}

Input Schema

Name	Required	Description	Default
`duration`	No
`project_id`	Yes
`description`	No
`work_item_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	No
`duration`	No
`logged_by`	No
`created_at`	No
`created_by`	No
`project_id`	No
`updated_at`	No
`updated_by`	No
`description`	No
`workspace_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a work log is created and returns a WorkItemWorkLog object, but does not mention permissions, side effects, idempotency, or failure scenarios. This is minimal transparency for a mutation tool.

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 a one-sentence purpose followed by a compact, clearly labeled Args and Returns section. Every line adds value, and there is no unnecessary wording.

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

Completeness3/5

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

The tool is relatively simple, and the description covers the action, all parameters, and the return type. However, it omits usage context, behavioral details, and any error or permission considerations. Given the presence of an output schema, the return is covered, but the lack of annotations and guidance leaves gaps.

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 'Args' section adds meaningful context beyond the schema by explaining each parameter's purpose—e.g., 'UUID of the project', 'Duration of work in minutes', and 'Description of the work performed'. This helps the agent correctly populate the parameters, even though the schema provides types and defaults.

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 'Create a work log for a work item' with a specific verb and resource. It is distinct from sibling tools like create_work_item, list_work_logs, update_work_log, and delete_work_log, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. It only describes the action itself, leaving the agent to infer usage from the verb.

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

Deploy Server