Skip to main content
Glama

jira_search

Search Jira work items using JQL queries to find issues by project, status, assignee, priority, or date ranges. Returns matching items with key details for tracking and management.

Instructions

Search for Jira work items using JQL (Jira Query Language). Use to find issues by project, status, assignee, priority, created/updated dates, and more. Returns a list of matching work items with their key, summary, status, priority, and assignee. Common search patterns: 1) My work: 'assignee = currentUser()' 2) My active work: 'assignee = currentUser() AND status NOT IN (Done, Closed)' 3) Project issues: 'project = SSAS' 4) High priority: 'priority = High' or 'priority IN (High, Highest)' 5) Recent updates: 'updated >= -7d' (last 7 days) 6) Combine with AND/OR: 'project = SSAS AND status = Open AND assignee = currentUser()' 7) Sort results: add 'ORDER BY updated DESC' or 'ORDER BY priority DESC, created ASC'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesJQL (Jira Query Language) query string. Structure: field operator value [AND/OR field operator value] [ORDER BY field ASC/DESC]. Common fields: project, status, assignee, priority, created, updated, summary, description, type. Operators: = (equals), != (not equals), IN (list), NOT IN (exclude list), > < >= <= (comparison), ~ (contains text), IS EMPTY, IS NOT EMPTY. Functions: currentUser() (logged in user), now() (current time), startOfDay(), startOfWeek(). Time: Use formats like -7d (7 days ago), -2w (2 weeks), -1M (1 month). IMPORTANT QUOTING RULES: 1) Multi-word values MUST be in double quotes: status = "In Progress" 2) Email addresses MUST be quoted: assignee = "user@example.com" 3) Special characters (@, #, $, etc.) MUST be in quoted strings 4) Use currentUser() function instead of email when possible 5) List values in parentheses: status IN (Open, "In Progress", Blocked) Examples: 'assignee = currentUser() ORDER BY updated DESC' - your work by recent update, 'project = SSAS AND status = Open' - open issues in SSAS project, 'priority = High AND status != Done' - high priority incomplete work, 'assignee = currentUser() AND status NOT IN (Done, Closed)' - your active work, 'updated >= -7d AND project = SSAS' - SSAS project updated in last 7 days, 'status IN ("In Progress", "Work in progress") AND assignee = currentUser()' - in-progress items, 'assignee = "user@example.com" AND priority = High' - specific user's high priority work
results_limitNoMaximum number of results to return (default: 10, max: 100)
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior: it returns a list of matching work items with specific fields (key, summary, status, priority, assignee) and includes practical examples of JQL queries. However, it doesn't mention potential limitations like rate limits, authentication requirements, or pagination behavior, which would be helpful for a search 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 well-structured and front-loaded with the core purpose, followed by usage examples. While comprehensive, it could be more concise by reducing some redundancy with the schema (e.g., the schema already details JQL syntax). Every sentence adds value, but the length might be slightly excessive given the detailed schema.

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

Completeness4/5

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

For a search tool with no annotations and no output schema, the description does a good job covering purpose, usage, and parameter semantics. It provides output details (list of work items with fields) and practical examples. However, it lacks information on error handling, rate limits, or authentication context, which would improve completeness for an unannotated tool.

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?

The schema description coverage is 100%, so the baseline is 3. The description adds significant value by providing seven common search patterns with concrete JQL examples (e.g., 'assignee = currentUser()', 'updated >= -7d'), which illustrate how to construct queries beyond the schema's technical documentation. This enhances understanding of the 'query' parameter's practical application.

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 explicitly states the tool's purpose: 'Search for Jira work items using JQL (Jira Query Language).' It specifies the verb ('search'), resource ('Jira work items'), and method ('using JQL'), clearly distinguishing it from sibling tools like jira_get_issue (which retrieves a single issue) or jira_update_status (which modifies issues).

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?

The description provides explicit guidance on when to use this tool through seven common search patterns (e.g., 'My work', 'Project issues', 'Recent updates'), which serve as practical examples. It implicitly distinguishes from siblings by focusing on query-based retrieval rather than specific operations like adding labels or commenting, though it doesn't explicitly name alternatives.

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

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