Skip to main content
Glama
vilaabo

zephyr-scale-mcp

by vilaabo

create_test_results_bulk

Create execution results for multiple test cases of a single test run in one call. Returns an array of created result IDs.

Instructions

Create NEW executions (test results) for several test cases of one test run in a single call. Every element's testCaseKey must already be one of the run's items — the run's item list is fixed when the run is created and this tool cannot extend it. In each element only the fields you pass are sent. Default statuses: 'Not Executed', 'In Progress', 'Pass', 'Fail', 'Blocked' — case-sensitive internal names; instances may define custom ones. Durations (executionTime) are in milliseconds; dates are ISO 8601. scriptResults record per-step outcomes as { index (0-based), status, comment? }. matchEnvironment / matchUserKey apply to the whole batch and disambiguate run items when the same test case is included in the run several times. Returns the array of created result ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesOne entry per result to create; each targets an existing run item by testCaseKey
testRunKeyYesTest run (cycle) key, e.g. PROJ-R123
matchUserKeyNoRun-item selector, sent as the 'userKey' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item by its executor's Jira user key (e.g. 'JIRAUSER10000').
matchEnvironmentNoRun-item selector, sent as the 'environment' QUERY parameter (never in the body): when the same test case is included in the run as several items, targets the item with this environment (case-sensitive). Distinct from the 'environment' body field, which sets the environment recorded on the result.
Behavior4/5

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

With empty annotations, the description carries full burden. It discloses creation behavior, immutability of run items, optional field sending, default statuses, units (ms for time, ISO 8601 for dates), scriptResults format, and batch-level disambiguation via matchEnvironment/matchUserKey as query parameters. Lacks error case disclosure but is otherwise thorough.

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, well-organized paragraph of around 150 words. It front-loads the main purpose and every sentence provides necessary detail without redundancy. No wasted words.

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

Completeness4/5

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

Given the tool's complexity (bulk creation, multiple parameters, nuanced behavior), the description is largely complete: it covers prerequisites, default statuses, units, date format, per-step results, disambiguation, and return value. Lack of error handling or permission notes is a minor gap.

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%, but the description adds value beyond schema by clarifying the batch application of matchEnvironment/matchUserKey as query parameters, the requirement that testCaseKey be a run item, and the format of scriptResults. It enriches understanding of parameter behavior.

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 'Create NEW executions (test results) for several test cases of one test run in a single call.' It specifies the verb (create), resource (executions/test results), and scope (bulk), distinguishing it from single-creation sibling create_test_result and other bulk tools for different resources.

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 provides context on when to use: for bulk creation of results within a single run, with the constraint that testCaseKeys must already be run items. It implies exclusion of single-result operations but does not explicitly name alternatives or when not to use this tool.

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/vilaabo/zephyr-scale-mcp'

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