Skip to main content
Glama

redmine_search_issues

Search Redmine issues with flexible filters for project, status, assignee, author, tracker, priority, date ranges, and free text. Returns paginated summary results to help you find relevant issues.

Instructions

Search Redmine issues with flexible filters. Filter by project, status, author, assignee, tracker, priority, free-text, and date ranges (created/updated). Supports offset for pagination through total_count. Returns a summary list -- use redmine_get_issue for full details. NOTE: author/assigned_to/updated_by accept 'me' or a numeric user ID -- display names like 'Yuko Matsui' will fail (Redmine API returns 500). Use redmine_find_user to resolve a name to an ID first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field:direction (e.g. 'updated_on:desc', 'priority:desc', 'created_on:asc', 'id:asc')updated_on:desc
limitNoMax results to return (default: 25, max: 100)
queryNoFree-text search query (searches subject and description)
authorNoFilter by issue author: 'me' or a numeric user ID. Use redmine_find_user to resolve a name.
offsetNoSkip this many results -- use with limit to paginate. e.g. limit=100, offset=100 returns results 101-200.
statusNoFilter by status: 'open', 'closed', '*' (all), or a specific status nameopen
trackerNoFilter by tracker name (e.g. 'Bug', 'Feature', 'Task')
priorityNoFilter by priority name (e.g. 'High', 'Normal', 'Low')
project_idNoProject identifier (e.g. 'panama', 'bunkyodo') or numeric ID
updated_byNoFilter by issues that this user has updated (commented on or changed): 'me' or a numeric user ID.
assigned_toNoFilter by assignee: 'me' or a numeric user ID. Use redmine_find_user to resolve a name.
created_sinceNoOnly issues created on or after this date (YYYY-MM-DD)
created_untilNoOnly issues created on or before this date (YYYY-MM-DD). Combine with created_since for a range.
updated_sinceNoOnly issues updated on or after this date (YYYY-MM-DD)
updated_untilNoOnly issues updated on or before this date (YYYY-MM-DD). Combine with updated_since for a range.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses the 500 error when using display names for author/assigned_to/updated_by, which is a critical behavioral trait, and explains the correct input format ('me' or numeric ID).

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 compact and well-structured: purpose, filter list, pagination, summary-list pointer, and a crucial caveat. No redundant words; each sentence adds value.

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

Completeness5/5

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

For a 15-parameter search tool with no output schema, the description covers key behaviors: summary list, pagination via total_count, and the critical input constraint. It provides enough context for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers all 15 params with descriptions, so baseline is 3. The description adds a warning that display names will fail (Redmine API returns 500) and reinforces the need to resolve via find_user, which goes beyond the schema's wording.

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 opens with 'Search Redmine issues with flexible filters' and enumerates the filter dimensions, clearly distinguishing it as a search tool. It also differentiates from redmine_get_issue by noting it returns a summary list, making the resource and verb explicit.

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

Usage Guidelines5/5

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

The description explicitly directs users to redmine_get_issue for full details and to redmine_find_user for resolving names to IDs, offering clear alternative paths. It also explains pagination via offset and total_count.

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

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