Skip to main content
Glama
fleagne

Backlog MCP Server

by fleagne

backlog_get_projects

Retrieve project details from Backlog API, filtering by archived status or administrator access. Supports pagination with a maximum of 20 results per request and offset functionality for efficient data handling.

Instructions

Performs list project get using the Backlog Projects get API. Supports pagination, content filtering. Maximum 20 results per request, with offset for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoOnly applies to administrators. If true, it returns all projects. If false, it returns only projects they have joined (set to false by default).
archivedNoFor unspecified parameters, this form returns all projects. For false parameters, it returns unarchived projects. For true parameters, it returns archived projects.

Implementation Reference

  • The main handler function for the 'backlog_get_projects' tool. It validates input parameters using ProjectsParamsSchema, calls projectService.getProjects, and formats the response as MCP content.
    const handleGetProjects: ToolHandler = async (args) => {
    	try {
    		try {
    			const validatedParams = ProjectsParamsSchema.parse(args);
    
    			const text = await projectService.getProjects(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_get_projects' to its handler function handleGetProjects 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 for input validation of the backlog_get_projects tool parameters: archived (boolean, optional), all (boolean, optional, default false).
    export const ProjectsParamsSchema = z.object({
    	archived: z
    		.boolean()
    		.optional()
    		.describe(
    			"For unspecified parameters, this form returns all projects. For false parameters, it returns unarchived projects. For true parameters, it returns archived projects.",
    		),
    	all: z
    		.boolean()
    		.optional()
    		.default(false)
    		.describe(
    			"Only applies to administrators. If true, it returns all projects. If false, it returns only projects they have joined (set to false by default).",
    		),
    });
  • MCP Tool definition for 'backlog_get_projects', including name, description, and inputSchema derived from ProjectsParamsSchema.
    export const PROJECTS_TOOL: Tool = createTool(
    	"backlog_get_projects",
    	"Performs list project get using the Backlog Projects get API. " +
    		"Supports pagination, content filtering. " +
    		"Maximum 20 results per request, with offset for pagination.",
    	ProjectsParamsSchema,
    );
  • Initializes the ToolRegistry with ALL_TOOLS, which includes the backlog_get_projects tool.
    export const toolRegistry = new ToolRegistry(ALL_TOOLS);
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds useful context about pagination ('Maximum 20 results per request, with offset for pagination') and content filtering, which aren't obvious from the schema alone. However, it doesn't cover important aspects like authentication requirements, error conditions, or rate limits that would be helpful for a tool making API calls.

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 appropriately concise with two sentences that each serve a purpose: the first states the core functionality, and the second adds important behavioral constraints. There's no wasted verbiage, though it could be slightly more front-loaded by mentioning the pagination limit earlier.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters, 100% schema coverage, and no output schema, the description provides adequate but minimal context. It covers the pagination behavior and filtering capability, but doesn't explain the return format or what 'projects' actually contain. Given the lack of annotations and output schema, more detail about the response structure would be helpful.

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 schema description coverage is 100%, so both parameters are well-documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions for 'all' and 'archived'. It mentions 'content filtering' generally but doesn't explain how the parameters enable this filtering.

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 ('Performs list project get') and resource ('using the Backlog Projects get API'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from its sibling 'backlog_get_project' (singular vs. plural), which could cause confusion about when to use each.

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 like 'backlog_get_project' or 'backlog_get_issues'. It mentions pagination and filtering capabilities but doesn't specify scenarios where this tool is preferred over other list/retrieval tools in the sibling set.

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