Skip to main content
Glama
0xkillaflow

Redmine MCP Server

by 0xkillaflow

List issues

redmine_list_issues
Read-only

Search and filter issues across projects using status, assignee, tracker, dates, custom fields, saved queries, and pagination. Get a clear view of your board.

Instructions

Search and filter issues across one or all projects — the primary entry point for "what's on the board". Supports status/assignee/tracker/date/custom-field filters, saved queries, sorting, and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort column, optionally with ":desc", e.g. "priority:desc,updated_on".
limitNoMaximum number of issues to return (Redmine caps at 100).
offsetNoPagination offset (skip N issues).
includeNoAssociations to expand on each issue: "attachments" and/or "relations".
subjectNoFilter by subject text (substring match).
due_dateNoDue-date filter; same operator grammar as created_on.
query_idNoRun a saved query by its numeric id.
author_idNoAuthor (reporter) user id, or "me".
status_idNoStatus filter. A status id, or a shortcut: "open" (any open status), "closed" (any closed status), or "*" (any status). Defaults to open issues.
created_onNoCreation-date filter. Accepts Redmine operators, e.g. ">=2024-01-01", "<=2024-12-31", or "><2024-01-01|2024-06-30" for a range.
project_idNoProject id or identifier slug to scope to, e.g. "42" or "website".
tracker_idNoTracker id, e.g. "1" for Bug.
updated_onNoLast-updated-date filter; same operator grammar as created_on.
category_idNoIssue category id.
custom_fieldsNoCustom-field filters keyed by field id, e.g. { "5": "urgent" } (exact match). Only fields enabled as a filter in Redmine apply; others are silently ignored.
assigned_to_idNoAssignee user id, or "me" for the API key's own user.
fixed_version_idNoTarget version (milestone) id.
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read behavior. The description adds value by detailing the capabilities (filters, sorting, pagination), which helps the agent understand scope without repeating safety info. No contradictions.

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 a single, front-loaded sentence that efficiently conveys purpose and capabilities. No unnecessary words; every phrase adds value.

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

Completeness4/5

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

With 17 parameters and no output schema, the description covers the core filtering features and mentions sorting/pagination. It does not detail return values or pagination mechanics, but the agent can infer from limit/offset parameters. Adequate for a list tool with good annotations.

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?

Schema coverage is 100%, so the baseline is 3. The description provides a high-level overview of filter categories (status, assignee, tracker, date, custom-field) but does not add new meaning beyond the schema. It is adequate.

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 verb 'Search and filter issues' and resource 'issues', with scope 'across one or all projects'. It distinguishes itself from siblings like redmine_get_issue (single) and redmine_create_issue by calling it the 'primary entry point' for overview. The list of supported filters reinforces its purpose.

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

Usage Guidelines4/5

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

The description implies this tool is for 'what's on the board' and lists filters, making it clear when to use it for listing issues. It does not explicitly state when not to use it or name alternatives, but the context is sufficient for most agents.

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/0xkillaflow/agama-redmine-mcp'

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