Skip to main content
Glama
gmlee-ncurity

Redmine MCP Server

redmine_update_issue

Update existing Redmine issues by modifying fields, adding comments, attachments, and custom values.

Instructions

Update an existing issue in Redmine

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesIssue ID to update
notesNoUpdate notes/comment (in Markdown format)
subjectNoIssue subject/title
uploadsNoFile attachments to add (use redmine_upload_file first to get tokens)
due_dateNoDue date (YYYY-MM-DD)
status_idNoStatus ID
done_ratioNoCompletion percentage (0-100)
is_privateNoWhether the issue is private
start_dateNoStart date (YYYY-MM-DD)
tracker_idNoTracker ID
category_idNoCategory ID
descriptionNoIssue description (in Markdown format)
priority_idNoPriority ID
private_notesNoWhether the notes are private
assigned_to_idNoAssigned user ID
estimated_hoursNoEstimated hours
parent_issue_idNoParent issue ID
fixed_version_idNoTarget version ID
custom_field_valuesNoCustom field values as key-value pairs
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the purpose and offers no information about update behavior (e.g., whether unspecified fields are preserved, if permissions are needed, or what response is returned). This is a significant gap for a mutation tool.

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?

The description is a single sentence with no fluff or redundancy, making it highly concise. It front-loads the core purpose effectively. While more detail would be useful, conciseness itself is handled well.

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

Completeness1/5

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

For a tool with 19 parameters, nested objects, and no output schema or annotations, the description must provide substantial context about update semantics, required fields, and side effects. The single-sentence description provides almost no such context, leaving the agent without critical information.

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?

The input schema has 100% parameter description coverage, so the baseline is 3. The description adds no parameter-specific information beyond the schema, but since the schema already documents each of the 19 parameters, no deduction is warranted.

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 'Update an existing issue in Redmine' clearly specifies the verb (update) and the resource (issue), and explicitly states that it operates on existing issues. This distinguishes it from siblings like redmine_create_issue and redmine_delete_issue.

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 such as redmine_create_issue or redmine_update_journal. The description does not mention prerequisites, partial update semantics, or cases where another tool would be more appropriate.

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/gmlee-ncurity/redmine-mcp-server'

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