Skip to main content
Glama

Search Issues

jira_search
Read-only

Search Jira issues using JQL queries. Filter by project, customize returned fields, and paginate through results.

Instructions

Search Jira issues using JQL (Jira Query Language).

Args: ctx: The FastMCP context. jql: JQL query string. fields: Comma-separated fields to return. limit: Maximum number of results. start_at: Starting index for pagination. projects_filter: Comma-separated list of project keys to filter by. expand: Optional fields to expand. page_token: Pagination token from a previous search result (Cloud only).

Returns: JSON string representing the search results including pagination info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlYesJQL query string (Jira Query Language). Examples: - Find Epics: "issuetype = Epic AND project = PROJ" - Find issues in Epic: "parent = PROJ-123" - Find by status: "status = 'In Progress' AND project = PROJ" - Find by assignee: "assignee = currentUser()" - Find recently updated: "updated >= -7d AND project = PROJ" - Find by label: "labels = frontend AND project = PROJ" - Find by priority: "priority = High AND project = PROJ"
limitNoMaximum number of results (1-50)
expandNo(Optional) fields to expand. Examples: 'renderedFields', 'transitions', 'changelog'
fieldsNo(Optional) Comma-separated fields to return in the results. Use '*all' for all fields, or specify individual fields like 'summary,status,assignee,priority'labels,versions,priority,description,reporter,status,summary,created,issuetype,updated,assignee
start_atNoStarting index for pagination (0-based)
page_tokenNo(Optional) Pagination token from a previous search result. Cloud only — Server/DC uses start_at for pagination.
projects_filterNo(Optional) Comma-separated list of project keys to filter results by. Overrides the environment variable JIRA_PROJECTS_FILTER if provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already provide readOnlyHint=true, confirming this is a read-only operation. The description adds details about pagination (start_at, page_token) but does not disclose additional behavioral traits beyond what annotations offer.

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 with clear sections (Args, Returns) but is slightly verbose due to the JQL examples and parameter details. It is efficient but not exceptionally concise.

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?

The description explains the return value as a JSON string with pagination info. Combined with an output schema (as indicated by context signals), it provides enough information for an AI agent to understand the tool's input and output.

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?

With 100% schema coverage, the baseline is 3. The description enhances this by providing JQL examples, clarifying the expand parameter options, and noting pagination token usage (Cloud-only). This adds value beyond the schema 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 'Search Jira issues using JQL', which is a specific verb-resource combination. It distinguishes itself from sibling tools like jira_get_issue (single issue) and jira_get_board_issues (board-specific) by focusing on flexible JQL queries.

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

Usage Guidelines4/5

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

The description provides clear context that this tool is for general JQL-based searching, but does not explicitly state when to avoid it or list alternative tools for specific searches. However, the context is sufficiently clear for most scenarios.

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

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