Skip to main content
Glama

jira_search

Find Jira resources: issues, projects, boards, sprints, versions, or users. Use JQL, text, or filters to locate tickets, backlogs, and team work.

Instructions

Discover Jira resources. Use when asked "find tickets for...", "what's in the backlog", "show me my issues", "list projects", or "which board is for project X". Set resource: • "issues" (default) — search by text, JQL, project, status, assignee, issue type, or mine=true for your queue • "projects" — list all projects and their keys • "issue_types" — valid types and statuses for a project • "boards" — list boards (pass project to filter by project key); use this to find the boardId before fetching sprints or board_overview • "sprints" — sprints for a board (pass boardId); if you don't know the boardId, first use resource=boards • "board_overview" — active/future sprints with their issues for a board (pass boardId); use when asked "what's in the sprint", "show me the board", or "what's everyone working on" • "versions" — list fix versions/releases for a project (pass project; optionally pass query to filter by name substring). If the version you need does not exist, create it yourself with jira_version action=create — do NOT ask the user to make it in the Jira UI. • "users" — find users by name/email (pass query)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceNoWhat to search (default: issues)
mineNoReturn issues assigned to you (resource=issues only)
queryNoText search or user name query
jqlNoRaw JQL (resource=issues only, overrides other filters)
projectNoProject key filter or scope for issue_types/boards
statusNoStatus filter (issues only, or board_overview to filter issues by status)
assigneeNoAssignee username filter (issues only, or board_overview to filter issues by assignee)
issueTypeNoIssue type filter (issues only)
boardIdNoBoard ID (required for resource=sprints or board_overview)
sprintStateNoSprint state filter: active, future, closed (sprints and board_overview)
includeIssuesNoInclude issues per sprint in board_overview (default true)
maxResultsNoMax results (default 20)
startAtNoPagination offset (default 0)
Behavior3/5

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

No annotations provided, so description must disclose behavior. It does not explicitly state it is read-only or mention side effects, rate limits, or auth. However, as a search tool, the behavior is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear list, front-loaded purpose, and no unnecessary words. Each line serves a purpose.

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

Completeness5/5

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

Given the tool's complexity (13 params, 8 resource types), the description covers all usage scenarios, explains interdependencies, and provides examples. No output schema exists, but return values are not essential.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions, but the description adds value by explaining parameter context per resource type (e.g., mine works only for issues, boardId required for sprints/board_overview).

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 the tool discovers Jira resources and provides specific use cases ('find tickets for...', 'list projects'). It distinguishes from sibling tools by focusing on search/discovery.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use patterns are given for each resource type, along with guidance on chaining (e.g., use boards before sprints). It also tells when to use another tool (jira_version to create versions).

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/stubbedev/atlassian-mcp'

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