Skip to main content
Glama

search_issues

Search Jira issues using JQL queries to find specific tickets by project, status, assignee, or custom criteria. Returns issue keys and titles for quick identification.

Instructions

Search for Jira issues using JQL (Jira Query Language). Returns issue keys and titles. Use get_issue for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlYesJQL query string (e.g., "project = PROJ AND status = Open")
maxResultsNoMaximum number of results to return (default: 50)

Implementation Reference

  • The main handler function that executes the search_issues tool logic: parses JQL args, calls Jira API /search/jql, formats markdown response with issue keys and summaries.
    async handleSearchIssues(args: any) {
      try {
        const { jql, maxResults = 50 } = args;
    
        if (!jql) {
          throw new Error('jql query is required');
        }
    
        // Use POST with fields parameter to get key and summary
        const requestBody = {
          jql,
          maxResults,
          fields: ['summary'], // Only get summary, key is always included
        };
    
        const result = await this.apiClient.post('/search/jql', requestBody);
    
        // Format response with key and title
        let response = `# Search Results\n\n**JQL**: ${jql}\n\n`;
        response += `Found ${result.issues.length} issue(s)${result.isLast ? '' : ' (more available)'}\n\n`;
    
        if (result.issues && result.issues.length > 0) {
          result.issues.forEach((issue: any) => {
            const key = issue.key;
            const summary = issue.fields?.summary || 'No summary';
            response += `- **${key}**: ${summary}\n`;
          });
    
          response += `\nšŸ’” Use \`get_issue\` with issue key to get full details.`;
    
          // Add pagination info
          if (!result.isLast && result.nextPageToken) {
            response += `\n\n**More results available** - ${result.issues.length} shown.`;
          }
        } else {
          response += `No issues found matching the query.`;
        }
    
        return {
          content: [
            {
              type: 'text',
              text: response,
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: JiraFormatters.formatError(error),
            },
          ],
          isError: true,
        };
      }
    }
  • Input schema and description definition for the search_issues tool, used for validation and listing.
      name: 'search_issues',
      description: 'Search for Jira issues using JQL (Jira Query Language). Returns issue keys and titles. Use get_issue for full details.',
      inputSchema: {
        type: 'object',
        properties: {
          jql: {
            type: 'string',
            description: 'JQL query string (e.g., "project = PROJ AND status = Open")',
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of results to return (default: 50)',
          },
        },
        required: ['jql'],
      },
    },
  • src/index.ts:108-109 (registration)
    Tool call dispatching/registration in the main MCP server switch statement, routes to SearchHandlers.handleSearchIssues.
    case 'search_issues':
      return this.searchHandlers.handleSearchIssues(request.params.arguments);
Behavior3/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. It states the tool 'returns issue keys and titles' which describes output format, but doesn't mention important behavioral aspects like whether this is a read-only operation, authentication requirements, rate limits, pagination behavior, or error handling. The description adds some value but leaves significant gaps.

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 perfectly concise with just two sentences that each serve a clear purpose: the first explains what the tool does, the second provides crucial usage guidance. There's zero wasted language, and the most important information (the tool's purpose) is front-loaded.

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

Completeness3/5

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

For a search tool with 2 parameters (100% schema coverage) but no annotations and no output schema, the description provides adequate but incomplete context. It explains the basic purpose and distinguishes from siblings, but lacks behavioral details about the search operation's scope, limitations, or output structure beyond 'issue keys and titles'. The absence of annotations and output schema means more context would be helpful.

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 already fully documents both parameters (jql and maxResults). The description doesn't add any parameter-specific information beyond what's in the schema. It mentions JQL generally but doesn't provide additional syntax examples or constraints. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 tool's purpose with specific verb ('search') and resource ('Jira issues'), and distinguishes it from sibling tools by specifying it returns 'issue keys and titles' and directing users to 'get_issue for full details'. This differentiates it from other issue-related tools like get_issue, create_issue, or update_issue.

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?

The description provides explicit guidance on when to use this tool versus alternatives: 'Use get_issue for full details' clearly indicates this tool is for searching and returning basic information, while get_issue should be used when detailed information is needed. This helps the agent choose between sibling tools appropriately.

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

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