Skip to main content
Glama
GonzaloRando03

Redmine MCP Server

delete_wiki_page

Delete a wiki page from a Redmine project by specifying the project identifier and page title.

Instructions

Deletes a wiki page from a project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID (numeric) or identifier (string)
titleYesWiki page title to delete
Behavior2/5

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

Description does not disclose whether deletion is permanent, if it requires specific permissions, or if there are cascading effects (e.g., on page versions). As a destructive action, more context is needed, especially given the absence of annotations.

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 sentence, which is concise but somewhat under-specified for a deletion tool. It is front-loaded but lacks necessary detail.

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's destructive nature and no output schema, the description fails to specify return behavior, success indicators, or operational constraints. The context is insufficient for an AI agent to use safely.

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 provides 100% coverage for both parameters. Description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance parameter understanding.

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?

Description clearly states the action (deletes), the resource (wiki page), and the scope (from a project). It effectively distinguishes from sibling delete tools like delete_issue or delete_project.

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 alternatives, such as archiving or soft deletion. No mention of prerequisites or conditions for safe usage.

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