Skip to main content
Glama

Update meeting agenda item

update_meeting_agenda_item

Edit a meeting agenda item's title, notes, duration, position, presenter, or work package link. Only the fields you pass are changed; all others stay exactly as they are.

Instructions

Edit one agenda item: retitle it, rewrite its notes, retime, reorder or re-link it.

Use it for "give that item 20 minutes", "move it to the top" (position=1), "let Grace present it", or to fix a wrong work-package link. Only the parameters you pass are sent; everything else is left exactly as it is.

Returns the updated item in the same shape as add_meeting_agenda_item, including the fresh lock_version for a follow-up edit.

Pitfalls. Once the meeting is CLOSED its agenda is frozen — every write answers a validation error until the meeting is reopened with update_meeting(state='open'). The item's type is fixed at creation: itemType is create-only upstream, so this tool never sends it and a simple item stays a simple item. A 422 otherwise usually means the presenter or work package is not visible in the project — violations names the attribute. This needs the 'manage agendas' permission (403 otherwise), and a 409 means a concurrent edit — the error carries the fresh lock_version.

Cross-references: get_meeting for the item ids, current values and lock versions; delete_meeting_agenda_item to remove the item; add_meeting_outcome to record what was decided under it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoNew markdown notes; they REPLACE the existing text, so read the current one with get_meeting first if you mean to extend it. Pass null or an empty string to clear. Omit the parameter entirely (the default) to leave it untouched.__unchanged__
titleNoNew item title. Omit to leave it alone; it cannot be cleared, because simple items require one.
positionNoNew 1-based position within the item's section — this is how the agenda is reordered; the other items shift around it. Omit to keep the order.
lock_versionNoThe item's lock_version as read from get_meeting. Pass it and the write fails loudly (409) on a concurrent edit; omit it and the current version is fetched and echoed.
presenter_idNoUser id of the new presenter, from search_principals or the meeting's participants. They must be able to view meetings in the project. Omit to leave the presenter alone.
agenda_item_idYesNumeric agenda item id from get_meeting's agenda_items (or from add_meeting_agenda_item's result). Not the meeting id, not a work package id.
work_package_idNoRe-point a work-package item at another work package, which must be visible to this account. Omit to leave the link alone; a simple item cannot be turned into a work-package one (itemType is create-only).
duration_minutesNoNew planned length of this item in minutes (0-1440). Omit to leave it as it is.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAgenda item id (not the meeting id, not a work package id).
notesNoItem notes as markdown (raw); html is dropped.
titleNoItem title. Empty for a work-package item, where the work package's subject is the title shown in the UI.
meetingNoMeeting the item was added to.
sectionNoAgenda section the item sits in, when the meeting uses sections.
outcomesNoOutcomes recorded against this item; always a list, empty when none.
positionNo1-based order within the agenda.
item_typeNo'simple' for a free-text item, 'work_package' for a linked one.
presenterNoUser presenting this item.
created_atNoISO 8601 UTC timestamp.
lock_versionNoOptimistic-lock version. Echo it as update_meeting_agenda_item's lock_version so a concurrent edit fails loudly (409) instead of being overwritten.
work_packageNoWork package this item discusses. Null both when none is linked and when the linked one is invisible to this account — 'notes' says when the latter happened.
duration_minutesNoPlanned length in minutes; null when the organizer set none.
Behavior5/5

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

While annotations indicate readOnlyHint=false and destructiveHint=false, the description adds rich behavioral context: only passed parameters are sent, the fresh lock_version is returned, closed meetings reject writes, itemType is create-only, permission requirements (403), and concurrency conflict semantics (409). This goes far beyond what annotations provide and avoids contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than the calibration examples, but every sentence earns its place: overview, examples, return value, pitfalls, and cross-references. It is well structured and front-loaded with the primary purpose, though the density could be slightly reduced without loss.

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 mutation complexity, the description covers partial update semantics, return shape, error cases (422, 403, 409), prerequisites (permissions, open meeting), and cross-references. Even with an output schema present, the behavioral and edge-case coverage is complete and actionable.

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?

The input schema already provides 100% coverage with detailed per-parameter descriptions. The tool description adds overarching context like 'Only the parameters you pass are sent' and the meaning of position for reordering, which clarifies interaction between parameters. Schema already carries the load, so the description only needs to add a little 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?

The description opens with a specific verb and resource: 'Edit one agenda item: retitle it, rewrite its notes, retime, reorder or re-link it.' This clearly distinguishes the tool from siblings like `add_meeting_agenda_item` and `delete_meeting_agenda_item`, using action-oriented language with concrete examples.

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 provides explicit usage scenarios ('Use it for...'), plus cross-references to related tools (`get_meeting`, `delete_meeting_agenda_item`, `add_meeting_outcome`). It also states when NOT to use it, e.g., when the meeting is CLOSED. This gives the agent clear decision-making guidance.

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