redmine-mcp-workflows

redmine_list_news

Retrieve news entries from Redmine's global feed or a specific project, with pagination support.

Instructions

List news entries (global feed, or scoped to a project).

Args: project: numeric id or identifier slug. Empty for the global feed across every project the API key can see. limit: page size (capped server-side at 100). offset: skip the first N results.

Returns {news, total_count, limit, offset, source}. Read-only.

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_news"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`project`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Declares 'Read-only' and explains pagination behavior (limit cap, offset) and return structure. With no annotations, this provides solid behavioral context, though error cases are omitted.

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?

Extremely concise: one-sentence purpose, structured Args block, final line for returns. No fluff, all sentences essential.

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?

Covers purpose, parameters, return shape, and read-only nature. Lacks error handling details, but for a simple list tool with output schema, this is near-complete.

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

Parameters5/5

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

Adds full semantic value for all 3 parameters: project format (numeric/slug, empty=global), limit cap, offset behavior. Schema coverage is 0%, so description carries the entire burden and does so excellently.

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?

Explicitly states action 'List news entries' with scoping options (global or project), clearly distinguishing from sibling tools like redmine_create_news or other list tools.

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?

Describes when to use (listing news) and the difference between global and project-scoped, but lacks explicit when-not-to-use or comparison to alternatives like redmine_search.

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

Deploy Server