Skip to main content
Glama
cosmix

JIRA MCP Server

by cosmix

search_issues

Search JIRA issues using JQL queries to find specific tickets, track project status, or identify related problems within your workflow.

Instructions

Search JIRA issues using JQL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchStringYesJQL search string

Implementation Reference

  • Core handler function that executes the JIRA issue search using JQL, fetches from REST API /rest/api/3/search, cleans issues using cleanIssue helper, and returns SearchIssuesResponse.
    async searchIssues(searchString: string): Promise<SearchIssuesResponse> {
      const params = new URLSearchParams({
        jql: searchString,
        maxResults: "50",
        fields: [
          "id",
          "key",
          "summary",
          "description",
          "status",
          "created",
          "updated",
          "parent",
          "subtasks",
          "customfield_10014",
          "issuelinks",
        ].join(","),
        expand: "names,renderedFields",
      });
    
      const data = await this.fetchJson<any>(`/rest/api/3/search?${params}`);
    
      return {
        total: data.total,
        issues: data.issues.map((issue: any) => this.cleanIssue(issue)),
      };
    }
  • MCP server request handler for CallToolRequestSchema specifically for 'search_issues' tool: validates args.searchString, delegates to jiraApi.searchIssues, and returns formatted MCP response content.
    case "search_issues": {
      if (!args.searchString || typeof args.searchString !== "string") {
        throw new McpError(
          ErrorCode.InvalidParams,
          "Search string is required",
        );
      }
      const response = await this.jiraApi.searchIssues(args.searchString);
      return {
        content: [
          { type: "text", text: JSON.stringify(response, null, 2) },
        ],
      };
    }
  • src/index.ts:85-98 (registration)
    Registration of the 'search_issues' tool in the MCP server's ListToolsRequestSchema response, including name, description, and input schema.
      name: "search_issues",
      description: "Search JIRA issues using JQL",
      inputSchema: {
        type: "object",
        properties: {
          searchString: {
            type: "string",
            description: "JQL search string",
          },
        },
        required: ["searchString"],
        additionalProperties: false,
      },
    },
  • TypeScript interface defining the output schema for the searchIssues function.
    export interface SearchIssuesResponse {
      total: number;
      issues: CleanJiraIssue[];
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the search method (JQL) but doesn't describe what the tool returns (e.g., issue list format, pagination, error handling), rate limits, or authentication requirements. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise with a single, clear sentence that directly states the tool's function without any fluff. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every word earns its place, achieving optimal brevity.

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 operation, lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances (e.g., search limits). While concise, it fails to provide enough context for an agent to use the tool effectively beyond the basic input parameter.

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 description adds no parameter-specific information beyond what the schema provides. Since schema description coverage is 100% (the single parameter 'searchString' is documented as 'JQL search string'), the baseline score of 3 is appropriate. The description doesn't elaborate on JQL syntax or examples, but the schema already covers the essential meaning.

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 action ('Search') and target resource ('JIRA issues') with the method ('using JQL'), making the purpose immediately understandable. It distinguishes from siblings like 'get_issue' by specifying search functionality rather than direct retrieval. However, it doesn't explicitly contrast with all siblings (e.g., 'get_epic_children' which also retrieves issues), keeping it from 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 where search is preferred over direct retrieval (e.g., 'get_issue' for single issues) or filtering options, nor does it specify prerequisites like authentication or JQL knowledge. This leaves the agent with minimal context for tool selection.

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

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