Skip to main content
Glama
testit-mcp-server

testit-mcp-server

by iampopovich

get_autotest_results_history

Read-only

Retrieve an autotest's result history across test runs, including status, outcome, run, plan, configuration, and duration, newest first, with filtering and pagination.

Instructions

Results of an autotest across test runs (status, outcome, run, plan, configuration, duration), newest first.

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>"
    },
    "name": "get_autotest_results_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAutotest UUID.
pageNo1-based page number; alternative to skip. Uses "size" (default 50).
sizeNoPage size for "page"; alias of take.
skipNoNumber of items to skip (offset).
takeNoMax number of items to return.
orderByNoSort expression, e.g. "createdDate desc".
testRunIdsNo
searchFieldNoField name to search in.
searchValueNoValue to search for in searchField.
statusCodesNoe.g. FAILED (list_test_statuses).
testPlanIdsNo
configurationIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds the default ordering ('newest first'), but says nothing about pagination limits, total counts, or how large histories are bounded — the behaviors most likely to surprise a caller with 12 parameters.

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?

A single dense sentence with the resource front-loaded and no filler. The parenthetical field list is compact, though it competes for space with guidance that would have been more valuable.

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?

For a 12-parameter read tool with no output schema, the definition covers what comes back and the default sort, which is the minimum viable set. It omits filtering guidance, pagination defaults, and any note on result volume, so an agent must read the schema to call it well.

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?

At 75% schema coverage the baseline is 3, and the description edges above it by mapping the parenthetical fields (status, run, plan, configuration) onto the filter parameters statusCodes, testRunIds, testPlanIds, and configurationIds, signaling what can be narrowed. It still leaves the page/size vs skip/take aliasing entirely to 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?

Names the resource precisely ('Results of an autotest across test runs') and enumerates the fields returned, which separates it from metadata tools like get_autotest. It does not, however, distinguish itself from history/result siblings such as get_work_item_test_results_history or get_test_run_results.

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?

There is no guidance on when to reach for this tool instead of the numerous other result/history tools in the sibling set, and no stated preconditions. The only contextual cue is the implicit 'history' framing.

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

Deploy Server

Other Tools