Redmine MCP Server

deleteNews

Delete a specific news item from Redmine by providing its ID and desired response format. Ensures removal of news entries via the Redmine API.

Instructions

Delete news

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>"
    },
    "name": "deleteNews"
  }
}

Input Schema

Name	Required	Description	Default
`pathParams`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Jun 10, 2026

TDQS

C2.5/5.0

Behavior2/5

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

The annotation readOnlyHint=false already indicates the tool performs a write operation, and the description is consistent with that. However, the description adds no additional behavioral context such as irreversibility, authorization requirements, or side effects, which would be valuable for a destructive action.

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

Conciseness2/5

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

The description is extremely brief (two words), which is under-specification rather than effective conciseness. It fails to convey essential information and does not front-load any helpful detail for the agent.

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 delete operation with nested parameters (newsId, format) and no output schema, the description offers no operational context. It does not explain what happens on success, error handling, or any effects on related data, leaving the agent without sufficient information to invoke the tool reliably.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It does not mention newsId or the format field, nor clarify what these parameters control. The description provides no semantic value over the schema.

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 'Delete news' uses a specific verb (delete) and a specific resource (news), clearly distinguishing it from siblings like deleteIssue and deleteProject. It exactly matches the tool's function with no ambiguity.

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, no mention of alternatives, and no conditions or exclusions. The description simply states the action without any context about when it is appropriate.

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

Deploy Server