Skip to main content
Glama

list_work_packages

List work packages from OpenProject using filters for status, assignee, dates, priority, and more. Supports sorting, grouping, and selecting specific fields.

Instructions

List work packages with structured filters and no free-text query requirement.

version_status filters by the status of a work package's assigned version: one of 'open', 'closed', or 'locked'.

assignee filters by any user (username, id, or "me"). assignee_me takes precedence.

status/priority filter by name or numeric ID (case-insensitive).

Date filters accept YYYY-MM-DD format:

  • created_on/updated_on/due_on: exact date match

  • created_between/updated_between/due_between: inclusive date range [start, end] Cannot specify both _on and _between for the same field.

sort_by accepts a list of sort criteria in format "field:direction" (e.g., ["status:desc", "priority:asc"]). Direction defaults to "asc" if omitted. Common sortable fields: id, subject, status, priority, type, assignee, author, created_at, updated_at, start_date, due_date.

group_by accepts a field name to group results by (e.g., "status", "assignee"). Common groupable fields: status, priority, type, assignee, author, version, category.

select restricts each result row to the given fields (e.g. ["id", "subject", "status"]); an invalid name returns the allowed set. Common fields: id, display_id, subject, type, status, priority, assignee, project, version, parent_id, start_date, due_date, estimated_time, spent_time, created_at, updated_at, author, category, description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNo
due_onNo
offsetNo
selectNo
statusNo
projectNo
sort_byNo
versionNo
assigneeNo
group_byNo
priorityNo
open_onlyNo
created_onNo
updated_onNo
assignee_meNo
due_betweenNo
version_statusNo
created_betweenNo
updated_betweenNo
Behavior4/5

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

Discloses filter behaviors, date format constraints, sort/group/select syntax, and mutual exclusivity of date parameters. Lacks details on pagination, default ordering, or error handling, but overall informative for a list tool with no annotations.

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?

Organized into logical sections (filters, dates, sort, group, select). Concise given the number of parameters covered. Could be slightly more streamlined, but generally well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers filtering and output customization thoroughly but lacks information on return format, pagination details, error behavior, or default sorting. Given 20 parameters and no output schema or annotations, the description is adequate but not fully comprehensive.

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

Parameters3/5

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

With 0% schema coverage, the description adds meaning for many parameters (version_status, assignee, status/priority, date filters, sort_by, group_by, select) but omits explanations for some (type, project, version, open_only, limit, offset). Provides value but not complete coverage.

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 verb 'List' and resource 'work packages'. Differentiates from 'search_work_packages' by explicitly mentioning 'structured filters and no free-text query requirement'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies when to use (structured filtering, not free-text) but lacks explicit guidance on when to prefer this tool over siblings like 'list_my_open_work_packages' or 'search_work_packages'. No 'use when' or 'avoid when' statements.

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/jtauschl/openproject-ce-mcp'

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