redmine-mcp

Overview Schema Source Related Servers Discussions Admin

List issues

issues_list

Read-onlyIdempotent

Lists Redmine issues using project, tracker, status, assignee, or saved-query filters, with pagination via offset and total_count for paging.

Instructions

Lists issues with Redmine filters (project, tracker, status, assignee, saved query). Returns the page plus total_count; pass offset to walk further pages.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort column and direction, e.g. "updated_on:desc".
`limit`	No	Issues per page (max 100).
`offset`	No	Pagination offset.
`include`	No	Associated data: children, attachments, relations, changesets, journals, watchers.
`subject`	No	Substring filter on the subject, applied client-side after the page is fetched.
`query_id`	No	Saved query id to run.
`status_id`	No	Status id, name, "open", "closed", or "*".
`project_id`	No	Project id or identifier to scope the list to.
`tracker_id`	No	Tracker id to filter by.
`assigned_to_id`	No	Assignee id, "me", or display name/login (resolved to an id before the call).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`issues`	Yes
`total_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.0Oct 23, 2026

changedInput schema / properties / assigned_to_id / description

Previous value: -"Assignee id or \"me\"."New value: +"Assignee id, \"me\", or display name/login (resolved to an id before the call)."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "issues": {
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "issues"
+  ],
+  "type": "object"
+}

First observedv0.2.0Oct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare it as a safe, idempotent read. The description adds that results are paged with a total_count, but that behaviour is largely restated by the 'limit'/'offset' schema descriptions, and it omits notable traits such as the subject filter being applied client-side after fetching.

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?

Two tight sentences, front-loaded with the core action and scope, with the pagination caveat last. Nothing is redundant or padded.

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 annotations covering safety, a full schema, and an output schema, the description need only orient the agent, which it does. A brief note on when to choose this over the related get/query tools would close the remaining gap.

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 every parameter is already documented with types and accepted values. The description lists filter categories (project, tracker, status, assignee, saved query) that map onto those parameters but adds no syntax or resolution detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('Lists issues') and enumerates the filter axes it accepts, so an agent knows exactly what it returns. It does not explicitly distinguish itself from nearby siblings like issues_get, queries_run, or search_query, which leaves some routing ambiguity.

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?

The clause 'pass offset to walk further pages' is real usage guidance for pagination, but there is no statement of when to prefer this over issues_get or queries_run. Usage is implied by the tool's name and filter list rather than stated.

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