Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

list_issues

Retrieve issues from Redmine using advanced filters, sorting, and pagination. Filter by status, project, assignee, dates, and more to find specific issues.

Instructions

Lists issues in Redmine with advanced filters, sorting and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of items to skip (default 0)
limitNoNumber of items per page (default 25, max 100)
sortNoSort field and direction. Examples: status:asc, priority:desc, updated_on:desc. Multiple: status:asc,priority:desc
includeNoComma-separated: attachments, relations, changesets, journals, watchers, allowed_statuses, children
issue_idNoFilter by issue ID(s). Comma-separated or range. Examples: 1,2,3
project_idNoFilter by project ID or identifier
subproject_idNoFilter by subproject. Use !* to exclude subproject issues
tracker_idNoFilter by tracker ID
status_idNoFilter by status. Values: open, closed, * (all), or numeric ID
priority_idNoFilter by priority ID
assigned_to_idNoFilter by assignee. Numeric ID or me for current user
author_idNoFilter by author ID
category_idNoFilter by issue category ID
fixed_version_idNoFilter by target version ID
parent_idNoFilter by parent issue ID
subjectNoFilter by subject. Use ~ prefix for contains: ~keyword
created_onNoFilter by creation date. Examples: >=2024-01-01, <=2024-12-31, ><2024-01-01|2024-12-31
updated_onNoFilter by last updated date. Same format as created_on
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'lists issues' without mentioning read-only, permissions, rate limits, or side effects. The lack of detail leaves the agent underinformed about non-obvious behaviors.

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 one sentence with no wasted words, but it is very brief. It could be expanded slightly to improve completeness without harming conciseness.

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

Completeness2/5

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

Given the tool has 18 optional parameters and no output schema or annotations, the description is too minimal. It fails to explain the output format, provide examples, or set expectations about default behavior or limitations.

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 description coverage is 100%, with each parameter documented. The description adds no additional parameter context beyond what the schema provides, so baseline 3 is appropriate as per guidelines.

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 lists issues in Redmine, with advanced filters, sorting, and pagination. It distinguishes from siblings like get_issue (single issue) and search (broader) by specifying the resource and capabilities.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this vs alternatives such as search or list_issues_by_sprint. The description implies using it for filtered listing but does not provide when-not-to-use or contrast with siblings.

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/GonzaloRando03/redmine-mcp-server'

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