Skip to main content
Glama

Delete meeting agenda item

delete_meeting_agenda_item
Destructive

Remove a meeting agenda item permanently. Deletes the item and its outcomes, shifts later items up, and leaves the meeting untouched.

Instructions

Permanently delete one agenda item, with any outcomes recorded against it.

Use only on explicit user instruction. The item and its recorded outcomes disappear from the agenda for good; the items after it move up. The meeting itself is untouched.

Returns a small confirmation object once OpenProject accepts the deletion.

Pitfalls. A CLOSED meeting's agenda is frozen: the delete answers a validation error, not a 403, until the meeting is reopened with update_meeting(state='open'). This needs the 'manage agendas' permission. A 404 means the id is wrong, the item is already gone — or, on OpenProject before 17.6, that the flat agenda-item write routes do not exist; the hint names all readings.

Cross-references: get_meeting to check which item the id points at; update_meeting_agenda_item when the item only needs fixing, not removing.

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.
agenda_item_idYesNumeric agenda item id to delete, from get_meeting's agenda_items. Check the item's title there first — it is not the meeting id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the meeting, agenda item, outcome or recurring series that was deleted.
deletedYesTrue once OpenProject accepted the deletion.
messageYesHuman-readable confirmation naming what was removed.
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that outcomes are permanently removed, items shift up, the meeting is untouched, a confirmation object is returned, closed meetings reject deletion, and a 404 can have multiple causes (including OpenProject version). This is rich behavioral context that annotations alone don't provide.

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 front-loaded with the main action, then efficiently covers implications, pitfalls, and alternatives. Every sentence adds value, and the structured pitfalls section improves scannability without 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?

Given the destructive nature and the existing output schema, the description covers return value, permission requirements, edge cases (closed meeting, version differences), and how to verify the target. It is fully complete for an agent to invoke correctly with minimal ambiguity.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds critical semantics: `agenda_item_id` is clarified as coming from `get_meeting` and being distinguished from meeting id, and `confirm` is explained with the exact failure mode (`confirmation_required` error) when false. This goes well beyond the schema descriptions.

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 starts with 'Permanently delete one agenda item, with any outcomes recorded against it' — a specific verb and resource. It distinguishes itself from the sibling `update_meeting_agenda_item` by stating that it removes rather than fixes, so the purpose is unambiguous.

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?

It explicitly says 'Use only on explicit user instruction' and provides cross-references: `get_meeting` to check the id, `update_meeting_agenda_item` for fixing instead of removing. This gives clear when-to-use and alternative guidance beyond the schema.

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