Skip to main content
Glama

jira_search_issues

Search for Jira issues using JQL queries to find, filter, and retrieve specific tickets from your Jira projects.

Instructions

Search for Jira issues using JQL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlYesJQL query string
max_resultsNoMaximum number of results to return

Implementation Reference

  • The handler function that implements the core logic for the 'jira_search_issues' tool. It extracts JQL and max_results from arguments, queries the Jira client, formats the issue data into a list of dictionaries (key, summary, status, assignee, priority, created, updated), and returns it as a JSON-formatted TextContent.
    async def _search_issues(self, arguments: dict) -> List[TextContent]:
        """Search for Jira issues"""
        jql = arguments["jql"]
        max_results = arguments.get("max_results", 50)
        
        results = self.jira_client.jql(jql, limit=max_results)
        issues = results.get("issues", [])
        
        formatted_issues = []
        for issue in issues:
            fields = issue.get("fields", {})
            formatted_issues.append({
                "key": issue["key"],
                "summary": fields.get("summary", ""),
                "status": fields.get("status", {}).get("name", ""),
                "assignee": fields.get("assignee", {}).get("displayName", "Unassigned") if fields.get("assignee") else "Unassigned",
                "priority": fields.get("priority", {}).get("name", "") if fields.get("priority") else "",
                "created": fields.get("created", ""),
                "updated": fields.get("updated", "")
            })
        
        return [TextContent(
            type="text",
            text=json.dumps(formatted_issues, indent=2)
        )]
  • Registration of the 'jira_search_issues' tool in the list_tools() method, including its name, description, and input schema definition.
    Tool(
        name="jira_search_issues",
        description="Search for Jira issues using JQL",
        inputSchema={
            "type": "object",
            "properties": {
                "jql": {
                    "type": "string",
                    "description": "JQL query string"
                },
                "max_results": {
                    "type": "integer",
                    "description": "Maximum number of results to return",
                    "default": 50
                }
            },
            "required": ["jql"]
        }
    ),
  • The input schema for the 'jira_search_issues' tool, defining parameters 'jql' (required string) and 'max_results' (optional integer, default 50).
    inputSchema={
        "type": "object",
        "properties": {
            "jql": {
                "type": "string",
                "description": "JQL query string"
            },
            "max_results": {
                "type": "integer",
                "description": "Maximum number of results to return",
                "default": 50
            }
        },
        "required": ["jql"]
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It doesn't disclose whether this is a read-only operation, its rate limits, authentication needs, pagination behavior, or what the return format looks like. The description only states what it does, not how it behaves.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it immediately clear without unnecessary elaboration.

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?

Given the complexity of a search tool with no annotations and no output schema, the description is insufficient. It doesn't explain return values, error handling, or behavioral constraints, leaving significant gaps for an AI agent to understand how to use it effectively.

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 description coverage is 100%, so the schema fully documents both parameters. The description adds no additional meaning beyond implying JQL usage, which is already covered in the schema's description of the 'jql' parameter. This meets the baseline for high schema coverage.

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 clearly states the verb ('Search') and resource ('Jira issues') with the method ('using JQL'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'jira_get_issue' or 'jira_get_projects', but the JQL focus implies a more flexible querying approach.

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 is provided on when to use this tool versus alternatives. It doesn't mention scenarios where this is preferable to 'jira_get_issue' (for single issues) or 'jira_get_projects' (for project lists), nor does it specify prerequisites like JQL knowledge or when not to use it.

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/katsuhirohonda/jira-confluence-mcp'

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