jira-mcp-server

search_issues

Find Jira issues by running a text query or JQL, returning matching results to assist with project management.

Instructions

Search for issues using a text query or JQL

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
`jql`	No	Advanced Jira Query Language (JQL) string
`query`	No	Text search query (searches summary and description)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic function without mentioning return format, pagination, whether it performs a read-only operation, or any permissions or limitations. For a search tool, this lacks essential behavioral context.

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?

The description is a single, front-loaded sentence with no extra words. It states exactly the main action and methods, maintaining high conciseness and clear structure.

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

Completeness2/5

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

With no output schema and only two parameters, the description is too minimal. It does not explain what the tool returns (e.g., list of issues), scope, or behavior when no parameters are provided. An agent would have incomplete context to fully expect the tool's behavior and limitations.

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 parameters are already described. The description adds the phrase 'text query or JQL', which clarifies the two modes but does not add details like whether both can be used together or any priority. This provides marginal value beyond the schema, aligning with the baseline for full schema coverage.

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 verb 'search' and the resource 'issues', with specific methods (text query or JQL). It distinguishes from sibling tools like get_issue by indicating a search operation rather than a single issue retrieval.

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 implies usage when you need to search for issues, but it does not explicitly state when to use versus alternatives such as get_issue, nor does it provide exclusions or conditions like 'use only if you have a query'. Guidance is implied, not explicit.

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