QTM4J: Get Automation History
qtm4j_get_automation_historyRetrieve paginated history of automation result uploads to review import status, audit CI/CD uploads, and paginate through past records.
Instructions
Retrieve a paginated history of past automation result uploads for a QTM4J project.
Toolset: Test Automation
Parameters:
startAt (number): Zero-indexed starting position for pagination (default: 0). (default: 0)
maxResults (number): Maximum number of records to return per page (default: 20, max: 100). (default: 20)
Output Description: Paginated list of automation import history. Each record includes: format, processStatus, importStatus, startTime, endTime, trackingId, detailedMessage, and a summary array. summary[0] contains: testCycleIssueKey, testCycleSummary, testCasesCreated, testCaseVersionsCreated, testCaseVersionsReused, testStepsCreated. Render as individual cards separated by dividers, NOT a table. Show '1–N of total' count above. Never show raw fileName.
Use Cases: 1. Review past automation result uploads for a project 2. Check the status of recent automation imports 3. Audit CI/CD automation upload history 4. Paginate through all historical automation uploads
Examples:
Get the first page of automation upload history (default page size 20)
{}Expected Output: Paginated list of automation history records with upload status and metadata
Get the second page of automation upload history
{
"startAt": 20,
"maxResults": 20
}Expected Output: Next 20 automation history records
Get up to 50 records starting from the beginning
{
"startAt": 0,
"maxResults": 50
}Expected Output: Up to 50 automation history records
Hints: 1. NO PROJECT CONTEXT REQUIRED: Do NOT call set_project_context and do NOT ask the user for a project key, project ID, or any other project details. This tool works independently. 2. PAGINATION: startAt is zero-indexed (default: 0), maxResults controls page size (default: 20, max: 100). Increment startAt by maxResults to fetch the next page. 3. Returns an empty data array (not an error) when no history records exist. 4. DISPLAY FORMAT: Show '1–N of ' above all cards. Render each record as a card separated by --- dividers. Each card has two sections:
PRIMARY SECTION (always first): heading with status emoji (✅ SUCCESS / ❌ FAILED) + test cycle key and name; then format, start→end time, message, summary stats (test cases/versions created/reused/test steps), tracking ID.
EXTRA DETAILS SECTION (at the bottom of the card, under a 'Details' sub-label): any remaining non-null fields from the record such as fileSize, extraAttributes values, etc.
Skip any field that is null, missing, or false. NEVER show the raw fileName. NEVER use a table.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| startAt | No | Zero-indexed starting position for pagination (default: 0). | |
| maxResults | No | Maximum number of records to return per page (default: 20, max: 100). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | ||
| total | No | ||
| startAt | No | ||
| maxResults | No |