Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_add_wiki

Create and add a wiki page to a Backlog project by specifying the project ID, page name, and content. Optionally enable email notifications for updates. Integrates with Backlog API for streamlined project documentation.

Instructions

Add an wiki using the Backlog Wiki API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent
mailNotifyNoTrue make to notify by Email
nameYesPage Name
projectIdYesProject ID

Implementation Reference

  • The handler function that executes the core logic of the 'backlog_add_wiki' tool: validates input using AddWikiParamsSchema, calls wikiService.addWiki, and formats the response.
    const handleAddWiki: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = AddWikiParamsSchema.parse(args);
    
    			const text = await wikiService.addWiki(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,
    		};
    	}
  • Maps the tool name 'backlog_add_wiki' to its handler function handleAddWiki in the toolHandlers registry.
    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,
    };
  • Zod schema defining the input parameters for the backlog_add_wiki tool, used for validation in the handler.
    export const AddWikiParamsSchema = z.object({
    	projectId: z.number().int().describe("Project ID"),
    	name: z.string().describe("Page Name"),
    	content: z.string().describe("Content"),
    	mailNotify: z.boolean().optional().describe("True make to notify by Email"),
    });
  • Defines the MCP Tool object for 'backlog_add_wiki', including name, description, and input schema conversion.
    export const ADD_WIKI_TOOL: Tool = createTool(
    	"backlog_add_wiki",
    	"Add an wiki using the Backlog Wiki API.",
    	AddWikiParamsSchema,
    );
  • Converts the Zod AddWikiParamsSchema to JSON Schema for the MCP tool inputSchema, with required fields specified.
    if (isAddWikiParamsSchema) {
    	return {
    		type: "object" as const,
    		properties: {
    			projectId: {
    				type: "number",
    				description: "Project ID",
    			},
    			name: {
    				type: "string",
    				description: "Page Name",
    			},
    			content: {
    				type: "string",
    				description: "Content",
    			},
    			mailNotify: {
    				type: "boolean",
    				description: "True make to notify by Email",
    			},
    		},
    		required: ["projectId", "name", "content"],
    	};
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Add an wiki' which implies a write operation, but doesn't cover permissions, side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with no wasted words. It directly states the tool's purpose without unnecessary elaboration, making it easy to parse and front-loaded with essential information.

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 as a write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after adding a wiki (e.g., success response, error cases), nor does it provide usage context or behavioral details. This leaves critical gaps for an AI agent to use the tool effectively.

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 already documents all parameters (projectId, name, content, mailNotify) with basic descriptions. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Baseline 3 is appropriate when the schema handles parameter documentation.

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 ('Add') and resource ('wiki'), specifying it uses the Backlog Wiki API. It distinguishes from siblings like backlog_delete_wiki or backlog_get_wiki by indicating creation rather than deletion or retrieval, though it doesn't explicitly contrast with backlog_update_wiki. The purpose is specific but lacks explicit sibling differentiation.

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 when to choose backlog_add_wiki over backlog_update_wiki or backlog_get_wiki, nor does it specify prerequisites or contexts for usage. This leaves the agent without direction on tool 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