Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

update_project

Update an existing Redmine project by specifying its ID and optionally modifying name, description, homepage, visibility, parent, modules, trackers, and custom fields.

Instructions

Updates an existing project in Redmine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID (numeric) or identifier (string)
nameNoProject display name
identifierNoProject identifier
descriptionNoProject description
homepageNoProject homepage URL
is_publicNoWhether the project is public
parent_idNoID of the parent project
inherit_membersNoInherit members from parent project
default_assigned_to_idNoDefault assignee ID for new issues
default_version_idNoDefault target version ID for new issues
default_issue_query_idNoDefault saved query ID for issue list
tracker_idsNoIDs of trackers available in this project
enabled_module_namesNoModule names: issue_tracking, time_tracking, news, documents, files, wiki, repository, boards, calendar, gantt
issue_custom_field_idsNoIDs of issue custom fields enabled for this project
custom_fieldsNoCustom field values for the project
Behavior2/5

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

With no annotations, the description carries the full burden. It only says 'updates', omitting any behavioral traits such as whether it is safe, requires specific permissions, or has side effects. The agent gets no risk cues.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise but too minimal. It lacks structure or front-loading of key information, making it less helpful despite brevity.

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 15 parameters and no output schema, the description is insufficient. It does not explain the update behavior, success indicators, or error conditions, leaving a significant gap for the agent.

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 coverage is 100%, so each parameter is described in the schema. The description adds no extra semantic value; baseline 3 is appropriate as the schema already documents parameters adequately.

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?

The description clearly states the tool updates an existing project in Redmine, which distinguishes it from creation (create_project) and deletion (delete_project) among siblings. However, it lacks specificity about what aspects can be updated.

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?

No guidance is provided on when to use this tool versus alternatives like archive_project or update_issue. The description does not mention prerequisites or context, leaving the agent to infer usage from the sibling names.

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