Skip to main content
Glama

jira_search

Search Jira issues with JQL to find items by project, status, assignee, labels, or sprint and return compact summaries for review.

Instructions

Search for Jira issues using JQL (Jira Query Language). Use this to find issues by project, status, assignee, labels, sprint, or any combination of criteria. Returns a compact summary per issue (key, summary, status, type, priority, assignee, reporter, labels, dates); use jira_get_issue for the description, comments and worklogs, or pass fields to include specific fields. Common JQL examples: "project = KP", "assignee = currentUser()", "status = 'In Progress'", "sprint in openSprints()", "labels = bug AND priority = High". For a shareable browser link to the same search, use jira_generate_filter_url.

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": "jira_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlYesJQL query string. Examples: "project = KP AND status = Open", "assignee = currentUser() ORDER BY updated DESC", "sprint in openSprints() AND status != Done"
fieldsNoExtra fields to add to the compact default, e.g. ["description", "comment", "customfield_10010"]. System keys and customfield_ ids pass through; display names (Severity) are resolved with a live GET /field, so prefer ids.
startAtNoStarting index for pagination
maxResultsNoMaximum number of results to return (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does well: it discloses the compact default return shape (key, summary, status, type, priority, assignee, reporter, labels, dates) which matters because there is no output schema. It stops short of stating error behavior for invalid JQL, default ordering, or any rate/result-cap caveats beyond the schema's own limits.

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 routing information is front-loaded and the sentences are purposeful. The enumerated JQL examples are somewhat bulky, but they are the tool's core input domain and justify their space; the paragraph is slightly longer than strictly necessary.

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

Completeness5/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 output schema and no annotations, the definition covers what the agent needs: query language with examples, return payload shape, the fields escape hatch, sibling routing, and where pagination lives (schema). Nothing material is missing for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3. The description adds real value on top: it explains why `fields` exists (to pull specific fields the compact summary omits) and supplies concrete JQL syntax examples that make the required `jql` parameter usable immediately, rather than just restating types.

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 opens with a specific verb and resource ('Search for Jira issues using JQL') and immediately separates this tool from jira_get_issue (detail/comments/worklogs) and jira_generate_filter_url (shareable link). An agent can distinguish it from all named siblings without inspecting schemas.

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?

It gives explicit when-to-use guidance ('find issues by project, status, assignee, labels, sprint'), names the alternatives jira_get_issue and jira_generate_filter_url with the conditions that select them, and points to the `fields` parameter for the middle ground of needing specific extra fields. Nothing is left to inference.

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