Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_update_time_entry

Idempotent

Edit an existing time entry's description, tags, start/end times, task association, or billable status. Correct logged entries or re-associate them with tasks.

Instructions

Edit an existing time entry's description, tags, times, task, or billable flag.

Calls PUT /team/{team_id}/time_entries/{time_entry_id}.

When to Use:

  • Correcting a logged entry's start/end, re-tagging it, or reassociating it with a different task.

When NOT to Use:

  • To manage tags across the whole Workspace (rename/remove the tag itself) — use clickup_rename_time_entry_tag / clickup_remove_time_entry_tags instead; this tool only changes which tags are on this entry.

  • To stop a running timer — use clickup_stop_time_entry.

Returns: A confirmation string, including the updated entry's detail when the API returns one.

Examples: params = {"team_id": "123", "time_entry_id": "abc", "tags": [{"name": "billing"}], "tag_action": "add"} params = {"team_id": "123", "time_entry_id": "abc", "start": 1700000000000, "end": 1700003600000}

Error Handling: 400 means start/end were given without their pair, or more than one tag action was implied; 404 means the time_entry_id doesn't exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Describes the API call, return type (confirmation string), and error handling (400, 404). Complements annotations: non-destructive, idempotent update operation. No contradictions.

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?

Well-structured with clear sections: purpose, when to use/not, returns, examples, error handling. Every sentence adds value; no fluff.

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

Completeness5/5

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

Covers usage boundaries, error cases, and examples comprehensively. The output schema exists but is not needed due to the clear return description. Fully adequate for the tool's complexity.

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?

Adds value beyond schema by showing example usage patterns and clarifying constraints like start/end pairing and tag_action rules. Schema already includes descriptions for most parameters, but the description provides real usage context.

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?

Clearly states 'Edit an existing time entry's description, tags, times, task, or billable flag.' Specific verb and resource, and distinguishes from siblings by naming alternatives for tag management and timer stopping.

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

Usage Guidelines5/5

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

Explicitly lists when to use (correcting logged entries) and when NOT to use, referencing sibling tools clickup_rename_time_entry_tag, clickup_remove_time_entry_tags, and clickup_stop_time_entry.

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/trustxai/clickup-mcp'

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