Skip to main content
Glama

Search Issues

jira_search
Read-only

Search Jira issues using JQL queries. Supports pagination, custom fields, project filtering, and expand options.

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"
fieldsNo(Optional) Comma-separated fields to return in the results. Use '*all' for all fields, or specify individual fields like 'summary,status,assignee,priority'reporter,status,priority,created,issuetype,summary,updated,labels,description,assignee
limitNoMaximum number of results (1-50)
start_atNoStarting index for pagination (0-based)
projects_filterNo(Optional) Comma-separated list of project keys to filter results by. Overrides the environment variable JIRA_PROJECTS_FILTER if provided.
expandNo(Optional) fields to expand. Examples: 'renderedFields', 'transitions', 'changelog'
page_tokenNo(Optional) Pagination token from a previous search result. Cloud only — Server/DC uses start_at for pagination.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations declare readOnlyHint=true, and the description adds context about pagination modes (page_token for Cloud vs start_at for Server/DC) and JQL flexibility. This supplements the annotation without contradiction.

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 an Args section and Returns line. However, it is slightly redundant given the schema descriptions, making it longer than necessary.

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?

Despite 7 parameters, the description covers core functionality (JQL usage, pagination) and references an output JSON string. With an output schema present (not shown), the description suffices for typical search operations.

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%, so the description repeats parameter details already present. It adds minimal extra context (e.g., clarifying page_token is Cloud-only), but largely restates what is in the schema.

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 searches Jira issues using JQL, which is distinct from other sibling tools like jira_get_board_issues or jira_get_project_issues. The verb 'search' and resource 'Jira issues' are specific.

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 (e.g., jira_get_board_issues, jira_search_fields). The description does not mention when not to use it or provide criteria for selection.

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