Skip to main content
Glama
trustxai

amazing-clickup-mcp

by trustxai

clickup_delete_time_entry

DestructiveIdempotent

Permanently delete duplicate, mistaken, or test time entries. Specify one or multiple IDs to remove them irreversibly.

Instructions

Permanently delete one or more time entries.

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

When to Use:

  • Removing a duplicate, mistaken, or test time entry.

When NOT to Use:

  • To stop (but keep) a running timer — use clickup_stop_time_entry.

Returns: A confirmation string naming the deleted id(s). This is irreversible.

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

Error Handling: 404 means the time_entry_id(s) don't exist or aren't accessible.

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?

Discloses the irreversible nature of the deletion and provides error handling details (404 for non-existent IDs), adding to the destructiveHint annotation.

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, front-loaded key action, and no redundant information.

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 preconditions, return type, error handling, and irreversibility; complete given the tool's simplicity and output schema.

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 covers param descriptions fully; description adds examples showing how to specify single or bulk IDs, adding minor extra value.

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 the tool deletes time entries, specifies the API endpoint, and distinguishes from other delete tools in siblings by specifically targeting time entries.

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 'When to Use' and 'When NOT to Use' sections, including a direct alternative (clickup_stop_time_entry) for stopping a running timer.

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