Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_update_wiki

Update a wiki page's content, title, or email notification settings using the Backlog Wiki API. Simplify collaboration and documentation management within projects.

Instructions

Update an wiki using the Backlog Wiki API.

Input Schema

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

Implementation Reference

  • The main handler function for the 'backlog_update_wiki' tool. Validates input using UpdateWikiParamsSchema and calls wikiService.updateWiki to perform the operation.
    const handleUpdateWiki: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = UpdateWikiParamsSchema.parse(args);
    
    			const text = await wikiService.updateWiki(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_update_wiki tool.
    export const UpdateWikiParamsSchema = z.object({
    	wikiId: z.number().int().describe("Wiki page ID"),
    	name: z.string().optional().describe("Page Name"),
    	content: z.string().optional().describe("Content"),
    	mailNotify: z.boolean().optional().describe("True make to notify by Email"),
    });
  • Registration mapping tool name 'backlog_update_wiki' to its handler function handleUpdateWiki.
    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,
    };
  • MCP tool definition for 'backlog_update_wiki' with name, description, and input schema.
    export const UPDATE_WIKI_TOOL: Tool = createTool(
    	"backlog_update_wiki",
    	"Update an wiki using the Backlog Wiki API.",
    	UpdateWikiParamsSchema,
    );
  • Core implementation making the PATCH API request to update the wiki page in Backlog.
    async updateWiki(params: UpdateWikiParams): Promise<string> {
    	const data = await this.request<BacklogWiki>(
    		`/wikis/${params.wikiId}`,
    		{ ...params, wikiId: undefined },
    		"PATCH",
    		{
    			"Content-Type": "application/x-www-form-urlencoded",
    		},
    	);
    	return JSON.stringify(data, null, 2);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's an update operation. It doesn't disclose behavioral traits like whether this requires specific permissions, if it overwrites or merges content, what happens to unspecified fields, or any rate limits/error conditions. 'Update' implies mutation, but details are missing.

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

Conciseness4/5

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

The description is a single, efficient sentence with no wasted words. However, it's front-loaded with minimal information and could benefit from slightly more detail to improve clarity without losing conciseness. It avoids redundancy but is overly brief.

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?

For a mutation tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover what the tool returns, error handling, or how updates interact with existing wiki data. Given the complexity and lack of structured data, more context is needed to guide effective use.

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 parameters are documented in the schema. The description adds no meaning beyond the schema—it doesn't explain parameter relationships (e.g., that 'wikiId' identifies the page to update, while 'name' and 'content' are fields to modify) or provide usage examples. Baseline 3 is appropriate since the schema handles documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Update') and resource ('wiki'), but it's vague about what specifically gets updated. It doesn't distinguish this tool from sibling 'backlog_update_issue' or clarify that it updates wiki content/settings rather than just metadata. The phrase 'using the Backlog Wiki API' is redundant with the tool name.

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 like 'backlog_add_wiki' (create) or 'backlog_update_issue' (update issues). The description doesn't mention prerequisites (e.g., needing an existing wiki ID) or contextual constraints. It's a basic statement with no usage context.

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