deleteNews
Remove a Redmine news entry by providing its ID and format (JSON or XML).
Instructions
Delete news
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pathParams | Yes |
Remove a Redmine news entry by providing its ID and format (JSON or XML).
Delete news
| Name | Required | Description | Default |
|---|---|---|---|
| pathParams | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It fails to disclose any behavioral traits such as side effects, idempotency, authorization, or what happens to related data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only two words, which is under-specified and lacks necessary detail. Conciseness should not sacrifice completeness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of delete operations and the presence of many sibling tools, the description is woefully incomplete. It does not explain the effect of deleting news or any related data.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds no meaning beyond the input schema. Schema coverage is 0%, but the schema itself defines the parameters. The description does not explain format or newsId.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete news' states the verb and resource, but is extremely terse and does not differentiate from sibling delete tools like deleteIssue or deleteProject.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 updateNews or createNews. No context or prerequisites provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/onozaty/redmine-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server