Skip to main content
Glama

update_work_log

Idempotent

Update the duration and description of an existing work log for a work item in a project to reflect actual work performed.

Instructions

Update a work log for a work item.

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

Returns: Updated WorkItemWorkLog object

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationNo
project_idYes
descriptionNo
work_log_idYes
work_item_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
durationNo
logged_byNo
created_atNo
created_byNo
project_idNo
updated_atNo
updated_byNo
descriptionNo
workspace_idNo
Behavior4/5

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

Annotations are present (idempotentHint=true, destructiveHint=false), and the description adds context by listing updatable fields and confirming the return of an updated object, without contradicting annotations.

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 description is structured as a docstring with args and returns, front-loaded with the purpose. Minor redundancy (repeating 'UUID of the') but overall efficient.

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 has an output schema and annotations, the description adequately covers the update operation. It could mention partial update behavior or error cases, but openness is acceptable with openWorldHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing clear meanings for all 5 parameters: UUIDs for IDs, duration in minutes, and description text.

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 specifies the action ('Update') and resource ('a work log for a work item'), distinguishing it from sibling tools like 'create_work_log' and 'delete_work_log'.

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?

The description implies usage for modifying existing logs but does not explicitly state when to use this tool versus creating or deleting, nor does it mention prerequisites like the log must exist.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Bl4nk44/plane-ce-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server