Skip to main content
Glama

clickup_time_update

Update a recorded time tracking entry by modifying specific fields like description, duration, start time, or billable status without affecting omitted fields.

Instructions

Modify a recorded time tracking entry. Only the supplied fields are changed; omitted fields keep their current value. Use clickup_time_add_tags / remove_tags for tag changes. Returns the updated time entry object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
billableNotrue = billable, false = non-billable. Omit to keep current value.
descriptionNoNew description for the entry. Omit to keep current description.
durationNoNew duration in milliseconds (e.g. 3600000 for one hour). Omit to keep current duration.
startNoNew start time as a Unix timestamp in milliseconds. Omit to keep current start.
team_idNoWorkspace (team) ID. Obtain from clickup_workspace_list (field: id). Omit to use the default workspace from config.
timer_idYesID of the time entry to update. Obtain from clickup_time_list (field: id).
Behavior4/5

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

With no annotations, the description explains partial-update semantics and return value, covering key behavior without listing errors or side effects.

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?

Three focused sentences with no filler—states purpose, partial update behavior, sibling alternatives, and output—ideal conciseness.

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 no output schema, it mentions return object; could note constraints like duration positivity, but overall sufficiently complete for an update tool.

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?

Schema already has 100% coverage with clear descriptions; the description adds value by reinforcing partial update and tag-related guidance.

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 modifies a time tracking entry and explicitly contrasts with siblings for tag changes, making its purpose distinct.

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

Usage Guidelines4/5

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

It specifies when to use this tool and directs to alternatives for tags, but lacks prerequisites or broader context like when to supply team_id.

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/nicholasbester/clickup-cli'

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