refine_backlog
Transform messy backlog items into structured work items with clear titles, acceptance criteria, size estimates, and priorities to improve project planning and execution.
Instructions
Refine messy backlog items into structured, actionable work items. Returns each item with a clean title, problem statement, acceptance criteria, T-shirt size estimate (XS/S/M/L/XL), priority with rationale, tags, and optional assumptions. Free tier: up to 5 items per request. Pro: 25. Team: 50.
BEFORE calling this tool, ask the user TWO quick questions if they haven't already specified:
Would you like titles formatted as user stories? ("As a [user], I want [goal], so that [benefit]")
Would you like acceptance criteria in Gherkin format? (Given/When/Then) Set useUserStories and useGherkin accordingly based on their answers. Both default to false.
LICENSE KEY: For unlimited requests and higher item limits, set REFINE_BACKLOG_KEY in your MCP server environment config (Claude Desktop → claude_desktop_config.json → env section). Get a key at https://refinebacklog.com/pricing
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Array of raw backlog item strings to refine. Each string is a rough description of work to be done. | |
| context | No | Optional project context to improve relevance. Example: "B2B SaaS CRM for enterprise sales teams" or "Mobile fitness app for casual runners". | |
| licenseKey | No | Optional. Refine Backlog license key for Pro or Team tier. Preferred: set REFINE_BACKLOG_KEY in your MCP server env config instead of passing inline. Get a key at https://refinebacklog.com/pricing. Free tier (5 items, 3 req/day) works without a key. | |
| useUserStories | No | Format titles as user stories: "As a [user], I want [goal], so that [benefit]". Default: false. | |
| useGherkin | No | Format acceptance criteria as Gherkin: Given/When/Then. Default: false. |