Skip to main content
Glama

backlog_create

Create a new backlog item with a title, optional description, parent links, and references. Supports tasks, epics, and cron items.

Instructions

Create a new item in the backlog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
descriptionNoTask description in markdown
source_pathNoLocal file path to read as description. Mutually exclusive with description — 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.
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. The single sentence 'Create a new item in the backlog' fails to mention side effects, permissions, ID assignment, or any constraints beyond what is in the schema. Important behavioral context like 'the item will be assigned an ID and stored' is 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 concise with one sentence and no fluff. However, it could be slightly longer to provide a brief summary of key points (e.g., required fields, conditional parameters) without becoming verbose.

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 (10 parameters, conditional fields like cron, mutual exclusivity of description and source_path, and no output schema), the description is insufficiently complete. It does not mention that cron type requires schedule and command, or that source_path is an alternative to description. An agent would need to read the entire schema to understand usage.

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 comprehensively. The description adds no additional meaning beyond what is in the schema, meeting the baseline expectation. No credit for repeating schema info.

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 'item in the backlog', effectively distinguishing it from sibling tools like backlog_delete or backlog_update. However, it could be more specific about the types of items (e.g., tasks, epics) which are covered 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 is provided on when to use this tool versus alternatives. For a tool with many siblings (backlog_update, backlog_search, etc.), explicit context on when creation is appropriate would significantly help an agent decide.

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