Skip to main content
Glama
gmlee-ncurity

Redmine MCP Server

redmine_delete_wiki_page

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

Instructions

Delete a wiki page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesWiki page title to delete
project_idYesProject ID or identifier
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Delete a wiki page' without revealing whether the deletion is permanent, requires special permissions, affects subpages, or returns a confirmation. This is a significant omission for a destructive operation.

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 efficient and front-loaded, but it is too terse to provide any value beyond the tool name. It is not verbose, but it also does not include any helpful extra context.

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?

For a destructive tool with no annotations and no output schema, this description is incomplete. It lacks crucial context about reversibility, permissions, and side effects, leaving the agent without a full understanding of what the deletion entails.

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 schema describes both parameters fully (100% coverage), so the description adds no additional meaning beyond the schema. The baseline of 3 applies because the structured data already documents the parameters.

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 action (delete) and the resource (wiki page), making the tool's primary purpose evident. However, it does not distinguish this tool from sibling delete tools like redmine_delete_issue or redmine_delete_time_entry, which is a minor gap.

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?

There is no guidance on when to use this tool versus alternatives such as redmine_create_or_update_wiki_page or redmine_get_wiki_page. It does not mention any prerequisites, scenarios for use, or when not to use it.

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