Skip to main content
Glama

manage_boards

Manage and organize Jira agile boards and sprints by listing, viewing, searching, creating, and moving issues.

Instructions

Manage Jira agile boards and sprints. Actions: 'list_boards', 'get_board', 'list_sprints', 'get_sprint_issues', 'get_backlog', 'get_active_sprint', 'search_sprints', 'create_sprint', 'move_to_sprint'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: 'list_boards', 'get_board', 'list_sprints', 'get_sprint_issues', 'get_backlog', 'get_active_sprint', 'search_sprints', 'create_sprint', 'update_sprint', 'move_to_sprint'
project_keyNoFilter boards by project key (for 'list_boards')
board_idNoBoard ID (for 'get_board', 'list_sprints', 'get_backlog', 'get_active_sprint', 'search_sprints', 'create_sprint')
sprint_idNoSprint ID (for 'get_sprint_issues', 'move_to_sprint')
stateNoSprint state filter: active, future, closed (for 'list_sprints')
queryNoSprint name search query (for 'search_sprints')
nameNoSprint name (for 'create_sprint')
start_dateNoSprint start date ISO 8601 (for 'create_sprint')
end_dateNoSprint end date ISO 8601 (for 'create_sprint')
goalNoSprint goal (for 'create_sprint')
issue_keysNoComma-separated issue keys (for 'move_to_sprint')
start_atNoPagination start index
max_resultsNoMaximum results to return
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as destructive actions, permissions needed, or rate limits.

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?

Concise single sentence with clear list of actions, but could be structured better with section breaks.

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?

No output schema, no annotations, and description lacks information about return values or side effects for actions.

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?

Input schema has 100% description coverage; the description adds no additional meaning beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it manages Jira agile boards and sprints, and lists specific actions, distinguishing it from sibling tools like manage_issues or manage_projects.

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 vs. alternatives; it simply lists actions without context about when each action is appropriate.

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/zach-snell/jtk'

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