Skip to main content
Glama

bulk_update_test_executions

Apply a single execution result, environment, or build to multiple test case executions in a test cycle using their map IDs.

Instructions

Apply the same execution result, environment, or build to multiple test case executions at once. Use testCycleTestCaseMapIds from get_test_cycle_executions (the 'testCycleTestCaseMapId' field). Returns 204 on success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cycleIdYesTest cycle ID
testCycleTestCaseMapIdsYesTest-case-execution map IDs to update
executionResultIdNoExecution result ID to apply to all
environmentIdNoEnvironment ID to apply to all
buildIdNoBuild ID to apply to all

Implementation Reference

  • The bulk_update_test_executions tool handler. Uses the 'tool' wrapper to register with the MCP server. Accepts cycleId, testCycleTestCaseMapIds (array of map IDs), and optional executionResultId, environmentId, buildId. Calls PUT /testcycles/{cycleId}/testcases/bulk and returns a success message.
    tool(
      "bulk_update_test_executions",
      "Apply the same execution result, environment, or build to multiple test case executions at once. Use testCycleTestCaseMapIds from get_test_cycle_executions (the 'testCycleTestCaseMapId' field). Returns 204 on success.",
      {
        cycleId: ID.describe("Test cycle ID"),
        testCycleTestCaseMapIds: z
          .array(z.number().int())
          .describe("Test-case-execution map IDs to update"),
        executionResultId: z.number().int().optional().describe("Execution result ID to apply to all"),
        environmentId: z.number().int().optional().describe("Environment ID to apply to all"),
        buildId: z.number().int().optional().describe("Build ID to apply to all"),
      },
      async ({ cycleId, ...rest }) => {
        await qtmFetch(`/testcycles/${cycleId}/testcases/bulk`, {
          method: "PUT",
          body: JSON.stringify(rest),
        });
        return ok({ message: "Bulk execution update applied" });
      }
    );
  • Input schema for bulk_update_test_executions: cycleId (string|number), testCycleTestCaseMapIds (array of ints), executionResultId, environmentId, buildId (all optional ints).
    {
      cycleId: ID.describe("Test cycle ID"),
      testCycleTestCaseMapIds: z
        .array(z.number().int())
        .describe("Test-case-execution map IDs to update"),
      executionResultId: z.number().int().optional().describe("Execution result ID to apply to all"),
      environmentId: z.number().int().optional().describe("Environment ID to apply to all"),
      buildId: z.number().int().optional().describe("Build ID to apply to all"),
    },
  • src/index.ts:172-183 (registration)
    The 'tool' helper/registration wrapper function that calls server.registerTool(), used by bulk_update_test_executions.
    const tool = <Shape extends z.ZodRawShape>(
      name: string,
      description: string,
      inputSchema: Shape,
      // eslint-disable-next-line @typescript-eslint/no-explicit-any
      callback: (args: z.infer<z.ZodObject<Shape>>) => Promise<any>
    ) =>
      server.registerTool(
        name,
        { description, inputSchema },
        // eslint-disable-next-line @typescript-eslint/no-explicit-any
        callback as any
Behavior3/5

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

Without annotations, the description discloses the return code (204) but omits behavioral details such as partial failure handling, idempotency, permissions, or the optional nature of the result/environment/build parameters.

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 concise with three sentences: purpose, usage hint, and return code. It is front-loaded and contains no extraneous information.

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?

Given the tool's complexity and lack of output schema, the description could provide more context on batch size limits, atomicity, and error handling to be fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for each parameter. The description adds value by explaining the source for testCycleTestCaseMapIds and clarifying the purpose of the update fields.

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 applies the same execution result, environment, or build to multiple test case executions at once, distinguishing it from single-update siblings like update_test_execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises using testCycleTestCaseMapIds from get_test_cycle_executions, providing a specific data source. However, it lacks explicit guidance on when to use this tool versus alternatives and does not mention prerequisites.

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/salehrifai42/qmetrymcp'

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