Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_get_time_entry_history

Read-onlyIdempotent

Retrieve the change history of a time entry to audit who modified its duration, description, or task association and when.

Instructions

View the list of changes made to a time entry.

Calls GET /team/{team_id}/time_entries/{time_entry_id}/history.

When to Use:

  • Auditing who changed a time entry's duration/description/task association and when.

When NOT to Use:

  • To read the entry's current state — use clickup_get_time_entry.

Returns: A markdown (default) or JSON list of raw change records as ClickUp returns them (field names vary by change type; this endpoint's payload shape isn't fully documented upstream, so entries render as key=value pairs rather than a fixed schema).

Examples: params = {"team_id": "123", "time_entry_id": "1963465985517105840"}

Error Handling: 404 means the time_entry_id doesn't exist or isn't accessible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate the tool is read-only, idempotent, and non-destructive. The description adds context about the HTTP method (GET), the variability of response fields, and output format options, which are behavioral traits not covered by annotations. It also explains error handling, enhancing transparency.

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 well-structured with headings for use cases, return values, examples, and error handling. Every sentence adds value, and there is no redundant or verbose language.

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?

Given the tool's simplicity (read-only history retrieval with a few parameters), the description covers purpose, usage, parameters, output format, and error handling comprehensively. The existence of an output schema does not detract, and the description properly acknowledges the upstream inconsistency.

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

Parameters3/5

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

Despite 0% schema description coverage, the description explains the key parameters: it gives an example with `team_id` and `time_entry_id`, mentions the default for `team_id` from environment variable, and alludes to `response_format` via output format discussion. This adds meaning beyond the bare schema, but lacks explicit mention of the `response_format` parameter name.

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 'View the list of changes made to a time entry', which is a specific verb+resource. It distinguishes from the sibling tool `clickup_get_time_entry` by noting that the latter is for reading current state, making the purpose clear and unique.

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?

Explicit sections 'When to Use' (auditing changes) and 'When NOT to Use' (to read current state, referencing `clickup_get_time_entry`) provide clear usage guidance. Error handling for 404 is also included, adding to the guidelines.

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