Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

list_projects

List Redmine projects with pagination and filters for status, name, description, date, and other criteria.

Instructions

Lists all projects in Redmine with pagination and optional filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoNumber of items to skip (default 0)
limitNoNumber of items per page (default 25, max 100)
includeNoComma-separated: trackers, issue_categories, time_entry_activities, enabled_modules, issue_custom_fields
statusNoFilter by status. Values: 1=active, 5=closed. Operators: = (default), ! (not equal). Examples: 1, 1|5, !1
idNoFilter by project ID. Special values: mine, bookmarks. Examples: 1|2|3, mine
nameNoFilter by project name. Operators: ~ (contains), !~ (not contains), ^ (starts with), $ (ends with)
descriptionNoFilter by description. Operators: ~ (contains), !~ (not contains), ^ (starts with), $ (ends with)
parent_idNoFilter by parent project. Operators: = (default), ! (not equal), * (any=subproject), !* (none=root). Values: ID, mine, bookmarks
is_publicNoFilter by public/private: 1=public, 0=private
created_onNoFilter by creation date. Examples: >=2024-01-01, t (today), >t-7 (last 7 days), lm (last month)
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 carries the full burden. It mentions pagination and filters but does not disclose any destructive actions, authentication requirements, rate limits, or details about the return data. It is a read operation but not explicitly marked as such.

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 a single, concise sentence that conveys the essential information without unnecessary words. It could slightly benefit from mentioning that it returns a list or notes about the default ordering, but it is well-structured.

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?

Given the lack of annotations and output schema, the description covers the tool's purpose and key features adequately for a listing tool. It could include more context about the response format or default behavior, but it is sufficient.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides by simply stating 'optional filters' without elaboration.

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 'Lists', the resource 'all projects in Redmine', and key features 'with pagination and optional filters'. This distinguishes it from sibling tools like get_project or search.

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 description implies usage for listing projects with filters and pagination but does not explicitly mention when to use this tool versus alternatives like search_in_project or get_project. No exclusions or comparisons are provided.

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