Skip to main content
Glama
Sign In
backlog-mcp-server

backlog-mcp-server

by mcpflow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

backlog_delete_wiki

Delete a wiki page in Backlog by specifying the wiki ID, with an optional email notification to users.

Instructions

Delete an wiki using the Backlog Wiki API.

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": {
      "wikiId": "<wikiId>"
    },
    "name": "backlog_delete_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
wikiIdYesWiki page ID
mailNotifyNoTrue make to notify by Email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior2/5

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

The description lacks detail about side effects, such as whether deletion is permanent, if it requires specific permissions, or if it affects related data. Given no annotations, the description should provide more behavioral context.

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 extremely short (one sentence), which makes it concise but at the expense of completeness. It could benefit from additional, well-structured details.

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 complexity (deletion with two parameters) and lack of output schema, the description is insufficient. It does not mention return values, error scenarios, or the effect of the optional mailNotify parameter.

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 coverage is 100%, and the description does not add extra meaning beyond the schema. The parameters are adequately described in the schema, so a baseline score of 3 is appropriate.

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 ('an wiki'), and it distinguishes from sibling tools like backlog_get_wiki or backlog_add_wiki. However, the grammar 'an wiki' is slightly awkward.

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 is provided on when to use this tool versus alternatives, such as backlog_update_wiki or backlog_get_wiki. There is no mention of prerequisites, conditions, or when deletion 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

Other Tools