Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_delete_wiki

Delete a wiki page using the Backlog Wiki API. Specify the wiki ID and optionally enable email notifications for confirmation. Streamlines wiki management within the Backlog MCP Server.

Instructions

Delete an wiki using the Backlog Wiki API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mailNotifyNoTrue make to notify by Email
wikiIdYesWiki page ID

Implementation Reference

  • The handler function for the 'backlog_delete_wiki' tool. It validates input parameters using DeleteWikiParamsSchema, calls wikiService.deleteWiki(), formats the result or error into the expected ToolResponse structure.
    const handleDeleteWiki: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = DeleteWikiParamsSchema.parse(args);
    
    			const text = await wikiService.deleteWiki(validatedParams);
    
    			return {
    				content: [
    					{
    						type: "text",
    						text: `Results for your query:\n${text}`,
    					},
    				],
    				isError: false,
    			};
    		} catch (validationError) {
    			throw new ValidationError(
    				`Invalid parameters: ${validationError instanceof Error ? validationError.message : String(validationError)}`,
    			);
    		}
    	} catch (error) {
    		return {
    			content: [
    				{
    					type: "text",
    					text: `Error: ${formatError(error)}`,
    				},
    			],
    			isError: true,
    		};
    	}
    };
  • Zod schema defining the input parameters for the backlog_delete_wiki tool: wikiId (required integer), mailNotify (optional boolean).
    export const DeleteWikiParamsSchema = z.object({
    	wikiId: z.number().int().describe("Wiki page ID"),
    	mailNotify: z.boolean().optional().describe("True make to notify by Email"),
    });
  • Registration of the tool handler: maps 'backlog_delete_wiki' to handleDeleteWiki in the toolHandlers record used by the MCP server.
    export const toolHandlers: Record<ToolName, ToolHandler> = {
    	backlog_get_projects: handleGetProjects,
    	backlog_get_project: handleGetProject,
    	backlog_get_issues: handleGetIssues,
    	backlog_get_issue: handleGetIssue,
    	backlog_add_issue: handleAddIssue,
    	backlog_update_issue: handleUpdateIssue,
    	backlog_delete_issue: handleDeleteIssue,
    	backlog_get_wikis: handleGetWikis,
    	backlog_get_wiki: handleGetWiki,
    	backlog_add_wiki: handleAddWiki,
    	backlog_update_wiki: handleUpdateWiki,
    	backlog_delete_wiki: handleDeleteWiki,
    };
  • Creation of the Tool object for 'backlog_delete_wiki' using createTool, including name, description, and input schema. Exported and included in ALL_TOOLS for registry.
    export const DELETE_WIKI_TOOL: Tool = createTool(
    	"backlog_delete_wiki",
    	"Delete an wiki using the Backlog Wiki API.",
    	DeleteWikiParamsSchema,
    );
  • Initialization of the ToolRegistry with ALL_TOOLS, which includes the backlog_delete_wiki tool, making it available to the MCP server.
    export const toolRegistry = new ToolRegistry(ALL_TOOLS);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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.

Install Server

Other Tools

Related Tools