Redmine MCP Server

redmine_list_time_entries

Retrieve time entries from Redmine using filters like date range, user, issue, or project to analyze logged hours.

Instructions

List time entries with optional filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "redmine_list_time_entries"
  }
}

Input Schema

Name	Required	Description
`to`	No	End date for range (YYYY-MM-DD)
`from`	No	Start date for range (YYYY-MM-DD)
`limit`	No	Maximum number of entries to return (1-100, default: 25)
`offset`	No	Number of entries to skip
`user_id`	No	User ID or "me"
`issue_id`	No	Issue ID
`spent_on`	No	Specific date (YYYY-MM-DD)
`project_id`	No	Project ID or identifier
`activity_id`	No	Time entry activity ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Aug 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure, yet it only states that the tool lists time entries with optional filters. It does not mention pagination, default limits, sorting, authentication requirements, or any other operational behavior. The schema reveals limit/offset parameters, but the description itself adds no behavioral detail.

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 a single concise sentence that states the core action and scope with no redundant wording. It is front-loaded and every word contributes to the meaning, making it highly efficient for an agent to parse.

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 9 optional parameters, no annotations, and no output schema, the description is under-specified. It lacks information about return structure, pagination behavior, filter combinations, or default values, leaving significant gaps for an agent deciding how to invoke the tool correctly.

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 the description is not required to document each parameter. The phrase 'optional filters' loosely encompasses the parameters but adds no meaning beyond what the schema already provides. This meets the baseline for full schema coverage.

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 uses a specific verb ('List') and resource ('time entries') with an explicit scope ('optional filters'), clearly distinguishing it from get_time_entry (single entry) and other list tools. It is unambiguous and immediately identifies the tool's function.

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?

The description offers no guidance on when to use this tool versus alternatives such as redmine_get_time_entry, redmine_create_time_entry, or redmine_list_time_entry_activities. There are no exclusions, prerequisites, or usage contexts provided beyond the basic listing action.

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