Skip to main content
Glama

List notifications

list_notifications
Read-onlyIdempotent

Fetch your OpenProject inbox notifications about mentions, assignments, and watched items, with filters for project, reason, and read/unread state.

Instructions

Read the authenticated user's OpenProject inbox.

Use this to answer "what needs my attention?", "was I mentioned anywhere?" or "what changed on the things I watch?" — it is the only tool that sees notifications, and it always reports the inbox of the token owner, never another user's.

Returns the standard list envelope: items of {id, reason, read, created_at, actor, project, resource} plus pagination with total/page/page_size/has_more. resource is the thing the notification is about — {id, type, title}, usually type='WorkPackage', so resource.id feeds straight into get_work_package or list_work_package_comments.

Pitfalls. Several changes to the same work package are aggregated into one notification, so the count is not a count of events. Reading a notification here does not mark it read — that is mark_notifications. unread_only=false can return a very long history; keep a page size that fits your reply. A notification whose project the token owner has lost access to disappears from the inbox entirely.

Cross-references: mark specific rows read with mark_notifications; clear the whole (optionally filtered) inbox with mark_all_notifications_read; open the underlying ticket with get_work_package(resource.id) and its discussion with list_work_package_comments(resource.id).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
reasonNoRestrict to one trigger: mentioned, assigned, responsible, watched, subscribed, commented, created, processed, prioritized, scheduled, shared, reminder, dateAlert. 'mentioned' is what answers "who needs me?". dateAlert filtering is an OpenProject Enterprise feature and is rejected with an explanatory hint on Community instances.
page_sizeNoNotifications per page (max 100); the instance may clamp it lower and the returned pagination reports what actually came back.
project_idNoNumeric project id or identifier to scope the inbox to one project. Ids come from list_projects.
unread_onlyNotrue (default) returns only notifications still unread in the in-app inbox; false returns read and unread together. There is no 'read only' mode — filter the rows on read=false/true yourself if you need one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sumsNoPresent only when show_sums was requested.
itemsNoThe page of results.
notesNoDegradation markers: capped aggregations, unavailable modules, …
groupsNoPresent only when group_by was requested.
paginationYesTotal/page/page_size/has_more.
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description reveals important behavioral traits: the inbox is always the token owner's, notifications aggregate multiple changes, reading here does not mark as read, unread_only=false may return a long history, and access loss causes notifications to disappear. It also notes the Enterprise-only dateAlert limitation. This significantly exceeds the annotation baseline.

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 structured with clear sections: purpose, example questions, envelope format, pitfalls, and cross-references. Every sentence adds practical information for a complex tool. It is front-loaded with the core purpose and stays efficient despite its length.

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?

Despite the output schema existing, the description provides a complete picture: return envelope structure, resource semantics, aggregation behavior, read-state implications, access edge cases, and explicit sibling tool handoffs. No major gaps remain for an agent to correctly invoke and interpret this tool.

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 coverage is 100%, so the baseline is 3. The description adds value by warning about 'unread_only=false can return a very long history' and advising page size tuning. It also clarifies that 'mentioned' is what answers 'who needs me?', but this is also in the schema. The extra context on unread_only and pagination justifies a 4.

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 the tool reads the authenticated user's OpenProject inbox, using the specific verb 'Read' and resource 'inbox'. It explicitly distinguishes itself from siblings by noting 'it is the only tool that sees notifications', making its purpose 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?

The description gives explicit 'Use this to answer' framing for common questions ('what needs my attention?') and provides alternatives via cross-references (mark_notifications, mark_all_notifications_read, get_work_package). This clearly tells the agent when to use this tool and what other tools handle related actions.

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