Redmine MCP Server

List Issues

list_issues

Retrieve and filter Redmine issues by project, status, assignee, tracker, or version, with pagination and sorting.

Instructions

List issues with optional filters and pagination.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort field and direction (e.g. "updated_on:desc").
`limit`	No	Maximum number of results per page (max 100).
`offset`	No	Pagination offset (ignored when fetch_all=True).
`fetch_all`	No	If True, automatically paginates and returns all matching issues in a single response.
`issue_ids`	No	Comma-separated list of issue IDs to fetch (e.g. "1,2,3").
`status_id`	No	Filter by status (e.g. "open", "closed", "*", or a numeric ID).
`project_id`	No	Filter by project ID.
`tracker_id`	No	Filter by tracker ID.
`assigned_to_id`	No	Filter by assignee user ID.
`fixed_version_id`	No	Filter by target version ID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions pagination but does not disclose default page size behavior, that fetch_all overrides offset, permission/auth requirements, or anything about the read-only nature beyond what "List" implies. For a 10-parameter query tool this is thin.

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?

A single front-loaded sentence with no wasted words. It is efficient, though the sparseness reads more as under-specification than deliberate compression.

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?

Ten parameters, no annotations, and an output schema present. Given that complexity, the description should at least gesture at the filter dimensions available and the fetch_all/limit/offset interaction; it says only "optional filters and pagination," which is not enough context for correct invocation.

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%, so every parameter already carries its own documentation, including the sort syntax, limit cap, offset, and fetch_all semantics. The description adds nothing beyond a generic reference to "filters and pagination," so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("List issues") and notes scope ("optional filters and pagination"), so an agent knows this is a read/query operation. However, it offers no differentiation from siblings like search or get_issue, leaving the agent to infer the boundary from the name alone.

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?

"With optional filters" implies a filtered-listing use case, but there is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as search or get_issue for single-issue retrieval. The agent gets no routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server