Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_get_wikis

Retrieve wiki pages from a Backlog project by specifying the project ID/key. Use keywords to filter and search relevant content within the wikis.

Instructions

Performs list wikis get using the Backlog Wiki API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNoKeyword for searching
projectIdOrKeyYesProject ID or Project Key

Implementation Reference

  • The main handler function for the 'backlog_get_wikis' tool. It validates input parameters using WikisParamsSchema, calls wikiService.getWikis to fetch the data, formats the response as text, and handles errors appropriately.
    const handleGetWikis: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = WikisParamsSchema.parse(args);
    
    			const text = await wikiService.getWikis(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,
    		};
    	}
    };
  • The toolHandlers object registers 'backlog_get_wikis' to the handleGetWikis function, mapping tool names to their handler implementations.
    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_get_wikis tool: requires projectIdOrKey, optional keyword.
    export const WikisParamsSchema = z.object({
    	projectIdOrKey: z.string().describe("Project ID or Project Key"),
    	keyword: z.string().optional().describe("Keyword for searching"),
    });
  • MCP Tool definition for 'backlog_get_wikis', including name, description, and input schema generated from WikisParamsSchema.
    export const WIKIS_TOOL: Tool = createTool(
    	"backlog_get_wikis",
    	"Performs list wikis get using the Backlog Wiki API",
    	WikisParamsSchema,
    );
  • wikiService.getWikis wrapper that delegates to the backlogAPI.getWikis method.
    async getWikis(params: WikisParams): Promise<string> {
    	try {
    		return await backlogAPI.getWikis(params);
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. It only states it 'performs list wikis get', which implies a read-only operation but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, error handling, or what 'list' entails (e.g., returns all wikis or a filtered set). This leaves significant gaps for an agent to understand how to use it effectively.

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 a single sentence, which is concise, but it's poorly structured with awkward phrasing ('list wikis get'). It could be more front-loaded and clearer, such as 'Lists wikis in a Backlog project, optionally filtered by keywords.' As is, it's minimally adequate but not efficient.

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 complexity of a list operation with parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain the return values, error cases, or how the listing behaves (e.g., pagination, sorting). For a tool that likely returns multiple items, more context is needed to guide an agent 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?

The input schema has 100% description coverage, with clear documentation for both parameters ('keywords' for searching and 'projectIdOrKey' as required). The description adds no additional meaning beyond the schema, such as explaining how keywords interact with listing or the format of project identifiers. Since schema coverage is high, the baseline score of 3 is appropriate.

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 tool 'Performs list wikis get using the Backlog Wiki API', which indicates it retrieves wiki entries. However, it's vague about the scope and doesn't differentiate from sibling tools like 'backlog_get_wiki' (singular) or 'backlog_get_issues'. The phrase 'list wikis get' is awkward and doesn't clearly specify if this lists all wikis, wikis in a project, or something else.

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. It doesn't mention prerequisites, such as requiring a project ID, or compare it to siblings like 'backlog_get_wiki' (which might fetch a single wiki) or 'backlog_get_issues' (for issues instead of wikis). The description lacks context for 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