testit-mcp-server

submit_test_run_results

Send autotest results into an existing test run by providing each result's autotest externalId and configurationId, then return the created test result IDs.

Instructions

Send autotest results into a test run (POST /testRuns/{id}/testResults). Each result needs an existing autotest externalId and a configurationId. Returns created test result IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "results": "<results>"
    },
    "name": "submit_test_run_results"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Test run UUID.
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds the real prerequisite that referenced autotests must exist and that created result IDs are returned. It does not address the non-idempotent hint (duplicate submission behavior) or what happens on partial batch failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: action+endpoint first, then prerequisites, then return value. Nothing is redundant, though the parenthetical endpoint could be trimmed if the name were self-evident.

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?

For an open-world mutating tool with no output schema, the description covers prerequisites and the shape of the return (created IDs). Remaining gaps are batch semantics, partial-failure behavior, and the non-idempotent nature, which matter for a results-submission endpoint.

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 coverage is only 50%, so the description must carry weight; it usefully constrains autoTestExternalId ('existing') beyond the bare string type. However, configurationId is left unelaborated (must it also reference an existing configuration?), and the per-result fields such as outcome vs statusCode and duration units are only partly covered by the schema.

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?

States a specific verb+resource ('Send autotest results into a test run') and pins it to POST /testRuns/{id}/testResults, which separates it from read-side siblings like get_test_run_results and from rerun_test_run_results. It stops short of naming an alternative, but the write-vs-read distinction is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied by the endpoint and by the prerequisite that the autotest externalId and configurationId must already exist, which is a useful precondition. There is no explicit when-to-use/when-not guidance against siblings such as rerun_test_run_results or create_test_run_from_autotests.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server