Skip to main content
Glama
Sign In
Redmine MCP Server

Redmine MCP Server

by onozaty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

updateWikiPage

Manage Redmine documentation by creating or modifying wiki pages. Use this function to update content, add files, and manage page versions directly through the Redmine MCP Server.

Instructions

Create or update wiki page

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pathParams": "<pathParams>",
      "bodyParams": "<bodyParams>"
    },
    "name": "updateWikiPage"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyParamsYes
pathParamsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • addedInput schema / properties / bodyParams / properties / wiki_page / properties / parent_title
      Added value: +{
+  "description": "Parent Wiki page title. Set a title to assign or change the parent, an empty string to remove it, or omit to preserve the current parent. Existing pages require rename_wiki_pages permission; read back to verify.",
+  "type": "string"
+}
    • addedInput schema / properties / bodyParams / properties / wiki_page / properties / uploads
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "content_type": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "filename": {
+        "type": "string"
+      },
+      "token": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  2. First observedv1.2.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, so the description must carry the behavioral burden and largely fails: nothing is said about required permissions, how version conflicts are handled, or what happens to fields not supplied on update. The only added signal is the upsert hint ("create or update"), which is genuinely useful but thin for a mutation tool with nested payloads.

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?

It is a single front-loaded phrase with zero waste, but this is under-specification rather than effective conciseness — there is simply not enough content to earn a higher score.

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?

A mutation tool with nested body params, no output schema, and minimal annotations needs substantially more: conflict/version semantics, permission needs, and update-vs-create behavior. Given that complexity, "Create or update wiki page" leaves the agent without what it needs to invoke the tool correctly.

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

Parameters2/5

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

Schema description coverage is 0% and the description provides no parameter information at all, so it does not compensate. The only parameter-level documentation lives in the schema itself (e.g., the parent_title description), meaning the description adds nothing about text, uploads, version, comments, or the projectId/wikiPageTitle path values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a resource (wiki page) and indicates upsert semantics ("create or update"), which adds a little beyond the name updateWikiPage. However, it is barely more than a restatement of the tool name and gives no scope details such as which project, what version behavior, or how it differs from sibling getWikiPage/getWikiPages/deleteWikiPage.

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 on when to use this tool versus getWikiPage, getWikiPageByVersion, or deleteWikiPage, and no prerequisites (e.g., permissions, existing page lookup) are stated. The create-vs-update condition is implied but never explained.

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

Deploy Server

Other Tools