Skip to main content
Glama

Delete time entry

delete_time_entry
Destructive

Permanently delete a logged time entry for genuinely wrong entries. No undo: removes booked hours from cost reports and the work package's spent time.

Instructions

Permanently delete a logged time entry.

Use only on explicit user instruction, and only for genuinely wrong entries. Deletion removes the booked hours from every cost report and from the work package's aggregated spent time, with no API-side undo.

Returns a small confirmation object once OpenProject accepts the deletion.

Pitfalls. If the entry is merely on the wrong day, has the wrong duration or the wrong activity, update_time_entry is the better answer — it keeps the audit trail. Deleting someone else's entry needs an administrative permission and otherwise fails with permission_denied. Entries inside a closed cost-reporting period cannot be deleted.

Cross-references: find the id with list_time_entries; correct instead of deleting with update_time_entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true. Ask the user to confirm first — the API offers no undo. Calling with confirm=false returns a confirmation_required error rather than deleting anything.
time_entry_idYesId of the time entry to delete permanently. It comes from list_time_entries — confirm the id belongs to the entry you mean before calling, since ids are not human-readable.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the time entry that was deleted.
deletedYesTrue once OpenProject accepted the deletion.
messageYesHuman-readable confirmation.
Behavior5/5

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

Adds significant context beyond annotations: deletion 'removes the booked hours from every cost report and from the work package's aggregated spent time, with no API-side undo.' Also discloses permission requirements, failure mode (permission_denied), and closed-period limitations.

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?

Front-loaded with the main purpose, then organized into usage, behavior, pitfalls, and cross-references. Every sentence carries necessary safety or usage information with no filler.

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?

For a destructive tool with a confirmation flag, this description covers when to use, how to confirm, side effects, failure modes, and alternatives. Output schema exists, so return format doesn't need explanation. Fully equips the agent for safe invocation.

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 both parameters at 100%, but description enriches their meaning: explains confirm must be true, the confirmation_required error when false, and that time_entry_id comes from list_time_entries and must be checked before calling. This adds practical workflow context beyond schema.

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?

Description opens with 'Permanently delete a logged time entry' — a specific verb and resource. It explicitly distinguishes itself from update_time_entry and list_time_entries through cross-references, making it unambiguous which tool to use.

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?

Provides explicit when-to-use guidance: 'Use only on explicit user instruction, and only for genuinely wrong entries.' Names update_time_entry as the better alternative for wrong day/duration/activity and notes permission and closed-period restrictions.

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/kar-thik/openproject-mcp'

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