Skip to main content
Glama
Sign In

MCP Server By TestMu AI

by com.lambdatest.mcp
OverviewDiscussionsAdmin

List HyperExecute Jobs

listHyperExecuteJobs
Read-only

List the account's HyperExecute jobs, newest first, with offset pagination and an optional status filter. The status filter looks at the 200 most recent jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listHyperExecuteJobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of jobs to return, 1 to 200 (default 10)
offsetNoNumber of jobs to skip, after the status filter (default 0)
statusNoOnly jobs with this status (e.g. completed, failed, running, skipped), among the 200 most recent

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of jobs to return"New value: +"Maximum number of jobs to return, 1 to 200 (default 10)"
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset"New value: +"Number of jobs to skip, after the status filter (default 0)"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by job status (e.g., completed, failed, running)"New value: +"Only jobs with this status (e.g. completed, failed, running, skipped), among the 200 most recent"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false). The description adds behavior beyond that: results are newest-first, pagination is offset-based, and critically the status filter only ranges over the 200 most recent jobs, which would otherwise cause silently incomplete results.

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?

Two sentences, no filler, with the core scope front-loaded and the filter limitation placed immediately after so it is read before the agent commits to a query.

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?

With no output schema, the description still gives an agent enough to call the tool correctly: scope, ordering, pagination and the filter window. It stops short of indicating what a returned job record contains, but that is a minor omission for a straightforward list 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 description coverage is 100%, so all three parameters are already documented in the schema, making 3 the baseline. The description's restatement of the 200-job filter window duplicates the status parameter description rather than adding new syntax or format detail.

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 and resource ('List the account's HyperExecute jobs') plus the ordering and pagination model, which cleanly separates it from the many single-job siblings like getHyperExecuteJobInfo and getHyperExecuteJobSessions. It does not explicitly name an alternative for the job-detail use case, but the list scope 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 rather than stated: an agent can infer this is for browsing jobs rather than inspecting one, and the 'status filter looks at the 200 most recent jobs' caveat is a genuinely useful boundary. However, there is no explicit when-to-use vs when-not, nor a pointer to the detail/artifact siblings for drilling into a specific job.

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

All MCP Server By TestMu AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources