Skip to main content
Glama

jira_search_issues

Search Jira issues using filters like status, assignee, project, labels, or raw JQL. Refine results with date ranges and text search.

Instructions

Search Jira issues with flexible filtering. Use individual filters (assignee, status, project, labels) or provide raw JQL for advanced queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlNoRaw JQL query (overrides all other filters when provided)
limitNoMaximum number of results (default: 50)
queryNoText to search for in issues
fieldsNoFields to include in the response. When specified, ONLY these fields are returned (plus issue key). When omitted, defaults to: summary, description, status, assignee, labels, created, updated. Use jira_get_fields to discover all available field IDs before using this parameter.
labelsNoFilter by labels (all must match)
statusNoFilter by status name (e.g., "To Do", "In Progress", "Done")
projectNoFilter by project key (e.g., "PROJ")
assigneeNoFilter by assignee. Use "currentUser()" for your own issues, or an account ID
reporterNoFilter by reporter. Use "currentUser()" for issues you reported, or an account ID
createdAfterNoShow issues created after this date. Use relative days (e.g., "10d" for last 10 days, "30d" for last 30 days) or absolute date (e.g., "2026-01-15")
updatedAfterNoShow issues updated after this date. Use relative days (e.g., "7d" for last 7 days) or absolute date (e.g., "2026-01-15")
Behavior3/5

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

No annotations provided, so description carries burden of transparency. It implies a read-only search operation but does not explicitly state no side effects, pagination behavior, or performance implications. Provides some context on filtering options but not thorough.

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?

Two succinct sentences: first states purpose, second outlines usage options. No redundant information, front-loaded, and easy to parse.

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

Completeness3/5

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

Description does not mention return format, ordering, or behavior when no filters are applied. Given the lack of output schema and 11 parameters, the description could be more comprehensive, but it adequately covers the core functionality.

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 coverage is 100% and each parameter has a detailed description. The tool description adds no additional meaning beyond summarizing the available filter types. Baseline 3 is appropriate.

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's purpose: 'Search Jira issues with flexible filtering'. It distinguishes from siblings like jira_get_issue (single issue) and other Jira tools by emphasizing flexible filtering and raw JQL support.

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

Usage Guidelines3/5

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

The description mentions using individual filters or raw JQL, but does not explicitly contrast with alternatives like jira_get_issue for single issues or when to prefer JQL over filters. Lacks explicit when-to-use guidance.

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/jagadeesh52423/ConfluenceMcp'

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