Skip to main content
Glama

jira_search_issues

Search Jira issues using JQL queries to find specific tickets, filter results by criteria, and retrieve relevant issue data for project tracking and management.

Instructions

Search for Jira issues using JQL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlYesJQL query string
startAtNoStarting index
maxResultsNoMaximum results to return
fieldsNoFields to include

Implementation Reference

  • MCP tool handler for 'jira_search_issues': validates arguments using schema, invokes JiraClient.searchIssues method, and serializes results as JSON.
    case "jira_search_issues": {
      const { jql, startAt, maxResults, fields } =
        SearchIssuesSchema.parse(args);
      const results = await jiraClient.searchIssues(
        jql,
        startAt,
        maxResults,
        fields
      );
      return {
        content: [{ type: "text", text: JSON.stringify(results, null, 2) }],
      };
    }
  • Zod schema defining input parameters for the jira_search_issues tool.
    const SearchIssuesSchema = z.object({
      jql: z.string().describe("JQL query string"),
      startAt: z.number().optional().default(0).describe("Starting index"),
      maxResults: z
        .number()
        .optional()
        .default(50)
        .describe("Maximum results to return"),
      fields: z.array(z.string()).optional().describe("Fields to include"),
    });
  • src/index.ts:230-250 (registration)
    Tool registration metadata exposed via ListToolsRequestHandler, including name, description, and input schema.
    {
      name: "jira_search_issues",
      description: "Search for Jira issues using JQL",
      inputSchema: {
        type: "object",
        properties: {
          jql: { type: "string", description: "JQL query string" },
          startAt: { type: "number", description: "Starting index" },
          maxResults: {
            type: "number",
            description: "Maximum results to return",
          },
          fields: {
            type: "array",
            items: { type: "string" },
            description: "Fields to include",
          },
        },
        required: ["jql"],
      },
    },
  • JiraClient method implementing the core search logic: POST request to Jira REST API /search endpoint with JQL query and pagination.
    async searchIssues(
      jql: string,
      startAt = 0,
      maxResults = 50,
      fields?: string[]
    ): Promise<JiraSearchResult> {
      return this.request<JiraSearchResult>("/search", {
        method: "POST",
        body: JSON.stringify({
          jql,
          startAt,
          maxResults,
          fields: fields || [
            "summary",
            "status",
            "assignee",
            "reporter",
            "priority",
            "created",
            "updated",
            "issuetype",
            "project",
            "description",
            "labels",
            "components",
          ],
        }),
      });
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose whether this is read-only, paginated, rate-limited, requires authentication, or returns structured data, which are critical for a search operation in Jira.

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 that front-loads the core purpose without unnecessary words. It's appropriately sized for a straightforward search tool, with zero wasted information.

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 tool's complexity (4 parameters, no output schema, no annotations), the description is insufficient. It lacks details on return format, pagination behavior, error handling, or JQL syntax examples, making it incomplete for effective agent use despite the concise structure.

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?

The schema description coverage is 100%, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying JQL usage, which is already covered by the 'jql' parameter's description. 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. However, it doesn't differentiate from sibling tools like 'jira_get_issue' or 'jira_search_users' beyond the general 'search' action, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like complex filtering, bulk retrieval, or comparisons to 'jira_get_issue' for single issues or 'jira_search_users' for user searches, leaving the agent without contextual usage cues.

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/yogeshhrathod/JiraMCP'

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