Skip to main content
Glama

search_test_sets

Search for test sets in Xray using JQL queries to find specific test collections for quality assurance and test management workflows.

Instructions

Search for test sets using JQL (Jira Query Language)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jqlYesJQL query to search test sets
maxResultsNoMaximum number of results to return

Implementation Reference

  • MCP server tool handler for 'search_test_sets'. Extracts JQL and maxResults from arguments, calls xrayClient.searchTestSets, and returns the result as JSON text content.
    case 'search_test_sets': {
      const result = await xrayClient.searchTestSets(
        args.jql as string,
        args.maxResults as number | undefined
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the 'search_test_sets' tool, specifying required JQL query and optional maxResults.
    inputSchema: {
      type: 'object',
      properties: {
        jql: {
          type: 'string',
          description: 'JQL query to search test sets',
        },
        maxResults: {
          type: 'number',
          description: 'Maximum number of results to return',
          default: 50,
        },
      },
      required: ['jql'],
    },
  • src/index.ts:427-445 (registration)
    Registration of the 'search_test_sets' tool in the MCP tools list, including name, description, and input schema.
    {
      name: 'search_test_sets',
      description: 'Search for test sets using JQL (Jira Query Language)',
      inputSchema: {
        type: 'object',
        properties: {
          jql: {
            type: 'string',
            description: 'JQL query to search test sets',
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of results to return',
            default: 50,
          },
        },
        required: ['jql'],
      },
    },
  • Core implementation of searchTestSets in XrayClient: executes GraphQL query to search test sets by JQL, returning paginated results with details.
    async searchTestSets(jql: string, maxResults: number = 50): Promise<any> {
      const query = `
        query SearchTestSets($jql: String!, $limit: Int!) {
          getTestSets(jql: $jql, limit: $limit) {
            total
            start
            limit
            results {
              issueId
              projectId
              jira(fields: ["key", "summary", "description", "status", "created", "updated"])
              tests(limit: 10) {
                total
                results {
                  issueId
                  jira(fields: ["key", "summary"])
                }
              }
            }
          }
        }
      `;
    
      const variables = {
        jql,
        limit: maxResults
      };
    
      const result = await this.graphqlRequest<{ getTestSets: any }>(query, variables);
      return result.getTestSets;
    }
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. It mentions JQL usage but fails to describe key traits: whether this is a read-only operation, potential rate limits, authentication needs, or what the output looks like (e.g., pagination, error handling). 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 a single, efficient sentence with zero wasted words. It front-loads the core purpose ('Search for test sets') and adds necessary detail ('using JQL') without redundancy. This is appropriately sized and well-structured for clarity.

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 with no annotations and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral constraints, leaving the agent under-informed. For a tool with 2 parameters and significant sibling tools, more context is needed to ensure proper usage.

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 ('jql' and 'maxResults'). The description adds no additional semantic context beyond implying JQL is used for searching, which is already covered in the schema. This meets the baseline of 3 when the schema handles parameter documentation effectively.

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 for') and resource ('test sets'), and specifies the query language ('using JQL'). It distinguishes from siblings like 'get_project_test_sets' by indicating a search function rather than a direct retrieval. However, it doesn't explicitly differentiate from other search tools (e.g., 'search_test_cases'), making it a 4 rather than a 5.

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 when to prefer this over 'get_project_test_sets' or other search tools, nor does it specify prerequisites or exclusions. This lack of contextual direction leaves the agent with minimal 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/c4m3lblue-star/xray-mcp'

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