Skip to main content
Glama

backlog_create

Create a backlog item with a required title and optional content, type, parent relationships, and cron scheduling for automated tasks.

Instructions

Create a new item in the backlog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
contentNoItem body in markdown
source_pathNoLocal file path to read as content. Mutually exclusive with content — provide one or the other. Server reads the file directly.
typeNoType: task (default) or epic
epic_idNoParent epic ID to link this task to
parent_idNoParent ID (any entity). Supports subtasks (task→task), epic membership, folder organization, milestone grouping.
referencesNoReference links. Formats: external URLs (https://...), task refs (mcp://backlog/tasks/TASK-XXXX.md), resources (mcp://backlog/resources/{path}). Local files must include extension (file:///path/to/file.md)
scheduleNoCron expression (5 fields: min hour dom month dow). Required when type=cron. Not permitted on other types.
commandNoScheduler-invoked command. Required when type=cron. Interpreted by an external scheduler (e.g. studio-agents schedule), not backlog-mcp itself.
enabledNoWhether the external scheduler should tick this cron. Defaults to true on cron creation. Separate from status — status answers "does this matter?", enabled answers "should it run?". Not permitted on non-cron types.
Behavior1/5

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

With no annotations, the description must disclose behavioral traits, but it only states 'create a new item.' It fails to mention side effects (e.g., file reading via source_path), required permissions, rate limits, or any constraints. This is a significant gap for a complex tool.

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 extremely concise at one sentence, which is efficient for a clear action. However, it could be slightly more informative without being verbose. The structure is front-loaded with the key action.

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

Completeness1/5

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

Given the tool's complexity (10 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain return values, error scenarios, or how to use advanced features like source_path or cron. This is inadequate for an AI agent to reliably invoke the tool.

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 description does not need to add parameter details. However, it adds no extra context beyond what the schema already provides, meeting the baseline but providing no additional value.

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 ('create') and the resource ('a new item in the backlog'), distinguishing it from siblings like backlog_update or backlog_delete. However, it lacks specificity on what types of items can be created (e.g., task, epic), which is only clarified in the schema.

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 on when to use this tool versus alternatives. It does not mention prerequisites, when to prefer backlog_create over backlog_update, or when not to use it. The description is purely functional 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

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

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