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);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool deletes a wiki, implying a destructive mutation, but lacks critical details: it doesn't specify if deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure. This leaves significant gaps in understanding the tool's behavior and risks.

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

Conciseness5/5

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

The description is a single, direct sentence with zero wasted words. It front-loads the key action ('Delete') and resource ('wiki'), making it immediately scannable and efficient. Every word earns its place, adhering perfectly to conciseness best practices.

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 (a destructive delete operation with no output schema and no annotations), the description is incomplete. It fails to address critical context like what the tool returns, error conditions, or safety warnings. For a mutation tool with significant behavioral implications, this leaves the agent under-informed about outcomes and risks.

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 description coverage is 100%, so the schema fully documents both parameters (wikiId and mailNotify). The description adds no additional meaning beyond what's in the schema, such as explaining parameter interactions or usage nuances. This meets the baseline score of 3, as the schema handles parameter documentation adequately.

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 resource ('an wiki'), making the purpose immediately understandable. It distinguishes from siblings like 'backlog_add_wiki' and 'backlog_update_wiki' by specifying deletion. However, it doesn't specify what 'wiki' refers to (e.g., a wiki page or entire wiki), leaving some ambiguity compared to more specific descriptions.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing wiki), exclusions, or comparisons to siblings like 'backlog_delete_issue' for context. The agent must infer usage from the tool name alone, which is insufficient for optimal selection.

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

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/fleagne/backlog-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server