Skip to main content
Glama

Search Jira issues

search_issues
Read-only

Find Jira issues by running JQL queries with a required bounding clause such as project, status, assignee, priority, or issue type.

Instructions

Search issues using JQL. Include at least one bounding clause: project, status, assignee, reporter, priority, type/issuetype, key, id, or created/updated/resolved. A project filter is optional. Quote JQL reserved values, for example project = "ON".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jql": "<jql>"
    },
    "name": "search_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlYesJQL query with at least one bounding clause.
limitNoMaximum issues to return.
fieldsNoFields to return. Default: summary, status, assignee, priority, updated, created, labels, issuetype.
config_idNoJira instance to use, from list_configs. Omit for the default.
next_page_tokenNonext_page_token from the previous page of this query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The bounding-clause requirement is a real behavioral constraint, but it is repeated almost verbatim in the jql schema description, so the description adds little beyond structured data; nothing about rate limits, result caps, or pagination behavior is mentioned.

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?

Three short sentences, front-loaded with the core action and the validity constraint, and the quoting hint is placed last where it belongs. The enumerated list of bounding clause types is slightly long but each item is actionable, so no sentence is wasted.

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 five-parameter, fully schema-covered read tool with annotations and no output schema, the description covers the essential calling constraints and one common failure mode (reserved-value quoting). Pagination and return-shape details are delegated to the schema, which is reasonable here.

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 baseline is 3; limit, fields, config_id, and next_page_token are all documented in schema. The description does add one piece of meaning beyond the schema — quoting JQL reserved values with the concrete example project = "ON" — but that is a narrow syntax tip rather than a substantive expansion of parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Search issues using JQL'), which is enough to separate it from single-issue siblings like get_issue or mutation siblings like update_issue. It stops short of explicitly naming an alternative, so it lands at clear-but-not-differentiating.

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?

It gives a concrete rule for a valid query (at least one bounding clause) and notes that a project filter is optional, which is useful query-construction guidance. However, it says nothing about when to reach for this tool versus get_issue or list-style siblings, leaving tool selection implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.