Skip to main content
Glama

List HyperExecute Jobs

tm.get_hyperExecuteJobs

Lists HyperExecute jobs, newest first, with status, labels, and test counts. Displays the Test Manager test_run_id for KaneAI-triggered jobs to link test runs to jobs.

Instructions

Lists every HyperExecute Job in the organization (not scoped to one specific job), newest first: job ID, job number, status, label, remark, task/test counts, who triggered it and how, timestamps, and execution time. When a job carries it, also shows its originating Test Manager test_run_id (from the job's meta.runId field) - the way to find which HyperExecute job corresponds to a known Test Manager test run. Not every job has this link (only KaneAI/Test-Manager-triggered jobs reliably do). Input: limit (page size, default 10, no documented hard maximum), cursor (a job_number to resume just below - from a previous response's 'Next Cursor' hint), show_test_summary (request the job_summary field - has returned null on every job observed so far, may not be populated for all job types). IMPORTANT: there is no way to filter or search directly by test_run_id/label server-side - finding a specific run's job means paging through results and checking each one's Test Manager Run ID. This can require checking many pages for an older run, since job numbers are not contiguous per organization. Read-only; does not modify anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
show_test_summaryNo
Behavior5/5

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

No annotations provided, so description carries full burden. Clearly explains read-only behavior, paging mechanism, null possibility of show_test_summary, and linking to Test Manager. Very transparent.

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?

Well-structured with listing, parameters, and important notes, but slightly verbose at over 150 words. Could be trimmed slightly without losing clarity.

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

Completeness5/5

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

No output schema exists, but description lists returned fields. Explains paging challenges and test_run_id linking. For a read-only listing tool with 3 params, this is complete and comprehensive.

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

Parameters5/5

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

Schema coverage is 0%, but description explains each parameter in detail: limit (page size default 10), cursor (resume from job_number), show_test_summary (request field with null behavior). Adds substantial meaning beyond schema.

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?

Describes listing all HyperExecute jobs in organization, specifying returned fields, and distinguishes from sibling tm.get_hyperExecuteJobById which targets a single job.

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?

States the tool is for listing many jobs not scoped to one, and provides guidance on paging due to lack of filtering by test_run_id. Could be more explicit about when not to use, but context is clear.

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/prakhar-gahlot/TestMu-AI-Test-Manager-MCP'

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