redmine-mcp-workflows

redmine_update_project

Update Redmine project details by sending only supplied fields—name, description, homepage, visibility, parent, trackers, or modules—without altering omitted settings.

Instructions

Update a project. Partial — only supplied fields are sent.

Args: project_id: numeric id or identifier slug. name: optional new display name. description: optional new description. homepage: optional new homepage URL. is_public: project visibility. None (omitted) leaves the current value unchanged — omitting never publishes a private project. parent_id: new parent project id (0 for unchanged). inherit_members: whether to inherit members from parent. None (omitted) leaves the current value unchanged. tracker_ids: optional list of tracker ids to enable. enabled_module_names: optional list of modules.

Returns the refreshed project. Honors REDMINE_MCP_READ_ONLY.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`homepage`	No
`is_public`	No
`parent_id`	No
`project_id`	Yes
`description`	No
`tracker_ids`	No
`inherit_members`	No
`enabled_module_names`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.1.0Sep 30, 2026
- addedInput schema / properties / inherit_members / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / inherit_members / default
```
Previous value: -falseNew value: +null
```
- removedInput schema / properties / inherit_members / type
```
Removed value: -"boolean"
```
- addedInput schema / properties / is_public / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- changedInput schema / properties / is_public / default
```
Previous value: -trueNew value: +null
```
- removedInput schema / properties / is_public / type
```
Removed value: -"boolean"
```
First observedv1.0.0Jul 9, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses partial semantics, the safe default that omitting is_public never publishes a private project, and that it honors REDMINE_MCP_READ_ONLY. It stops short of stating required permissions or failure behavior for invalid ids.

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?

Purpose is front-loaded in one sentence, followed by a tight per-argument list. The Args block is verbose but each line is justified by the total absence of schema descriptions, so nothing is wasted.

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?

For a 9-parameter mutation tool with no annotations and an output schema, the description covers the essentials: partial semantics, per-param meaning, the read-only guard, and return behavior. Missing only permission/prerequisite detail, which is a minor gap.

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?

Schema description coverage is 0%, so the description must compensate, and it does: every parameter gets meaning, including the non-obvious sentinel semantics ('parent_id: 0 for unchanged', is_public/inherit_members None leaves value unchanged). This adds real value beyond the bare types/defaults in the schema.

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?

Opens with a specific verb+resource ('Update a project') and immediately qualifies the mutation as partial ('only supplied fields are sent'). It does not explicitly differentiate itself from siblings such as redmine_create_project or redmine_archive_project, but the operation is unambiguous.

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 partial-update framing signals when this is appropriate (incremental edits without resending the whole project), but there is no explicit when-to-use/when-not guidance or named alternative (e.g., use redmine_archive_project to deactivate, redmine_create_project to add). Usage is only implied.

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

Deploy Server