Skip to main content
Glama

remove_tests_from_test_set

Remove specific tests from an existing test set in Xray test management by providing test set and test issue IDs.

Instructions

Remove tests from an existing test set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testSetIssueIdYesThe test set issue ID (not key)
testIssueIdsYesArray of test issue IDs to remove

Implementation Reference

  • Core handler function in XrayClient that executes the GraphQL mutation to remove tests from a test set in Xray Cloud.
    async removeTestsFromTestSet(testSetIssueId: string, testIssueIds: string[]): Promise<any> {
      const mutation = `
        mutation RemoveTestsFromTestSet($issueId: String!, $testIssueIds: [String]!) {
          removeTestsFromTestSet(issueId: $issueId, testIssueIds: $testIssueIds) {
            removedTests
            warning
          }
        }
      `;
    
      const variables = {
        issueId: testSetIssueId,
        testIssueIds
      };
    
      const result = await this.graphqlRequest<{ removeTestsFromTestSet: any }>(mutation, variables);
      return result.removeTestsFromTestSet;
    }
  • MCP server request handler (dispatch) that receives tool call parameters and invokes the XrayClient removeTestsFromTestSet method.
    case 'remove_tests_from_test_set': {
      const result = await xrayClient.removeTestsFromTestSet(
        args.testSetIssueId as string,
        args.testIssueIds as string[]
      );
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • src/index.ts:484-502 (registration)
    Tool registration in the MCP tools array, including name, description, and input schema definition.
    {
      name: 'remove_tests_from_test_set',
      description: 'Remove tests from an existing test set',
      inputSchema: {
        type: 'object',
        properties: {
          testSetIssueId: {
            type: 'string',
            description: 'The test set issue ID (not key)',
          },
          testIssueIds: {
            type: 'array',
            items: { type: 'string' },
            description: 'Array of test issue IDs to remove',
          },
        },
        required: ['testSetIssueId', 'testIssueIds'],
      },
    },
  • Input schema definition for the remove_tests_from_test_set tool, specifying parameters for validation.
    inputSchema: {
      type: 'object',
      properties: {
        testSetIssueId: {
          type: 'string',
          description: 'The test set issue ID (not key)',
        },
        testIssueIds: {
          type: 'array',
          items: { type: 'string' },
          description: 'Array of test issue IDs to remove',
        },
      },
      required: ['testSetIssueId', 'testIssueIds'],
    },
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 states a mutation action ('Remove') but doesn't clarify if this is destructive (e.g., permanently deletes tests or just unlinks them), requires specific permissions, has side effects (e.g., affects test executions), or provides any response details. This leaves critical behavioral traits unspecified for a mutation tool.

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 directly states the tool's action without unnecessary words. It's front-loaded with the core purpose, and every part of the sentence earns its place by specifying the resource ('tests from an existing test set'). No fluff or redundancy is present.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., destructiveness, permissions), response format, error handling, or how it fits within the broader test management context. For a tool that modifies data, this leaves significant gaps for an AI agent to operate safely and 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%, with both parameters ('testSetIssueId', 'testIssueIds') clearly documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no examples, format clarifications, or constraints). Baseline 3 is appropriate as the schema does the heavy lifting, but the description doesn't enhance parameter understanding.

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 ('Remove') and resource ('tests from an existing test set'), making the purpose immediately understandable. It distinguishes from siblings like 'remove_tests_from_test_plan' by specifying 'test set' rather than 'test plan'. However, it doesn't specify what type of tests (e.g., test cases) or how removal affects the test set, leaving some ambiguity.

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 prerequisites (e.g., needing an existing test set), exclusions (e.g., cannot remove all tests), or compare with siblings like 'delete_test_case' or 'update_test_case'. The agent must infer usage from the name and context alone.

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