Skip to main content
Glama

MCP Server By TestMu AI

Automation Query

automationQuery
Read-only

Read-only query of TestMu AI automation resources: list builds, get one build, list the sessions in a build, fetch test details, and retrieve test logs (command, network, console, selenium, instrumentation). Every combination works on platform "web" or "app": build list or get, session list or get, test get, and logs get with a logType. List results carry a pagination object; trust it, not result_set.total, which also counts older builds the list no longer returns. logType "instrumentation" returns XCUI and Espresso test logs. Renaming, stopping and deleting builds are separate tools: updateBuild, stopBuild and deleteBuild.

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": {
      "resource": "<resource>",
      "action": "<action>",
      "platform": "<platform>"
    },
    "name": "automationQuery"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order for build listing (e.g. "asc", "desc")
limitNoNumber of results to return, 1 to 100
actionYesThe read to perform: list, or get one
offsetNoOffset for pagination; pass the next offset from a previous response
statusNoFilter builds by status (e.g. "running", "passed", "failed")
testIdNoTest ID — required for test get and logs get
todateNoFilter builds to this date (YYYY-MM-DD, not before fromdate)
buildIdNoBuild ID — required for build get, optional filter for session list
logTypeNoLog type — required when resource is "logs"
fromdateNoFilter builds from this date (YYYY-MM-DD, a real calendar date)
platformYesThe platform type: "web" for browser automation, "app" for mobile app automation
resourceYesThe resource type to query
sessionIdNoSession ID: required for session get and for app platform log retrieval. Session get also accepts the test ID instead.
pageNumberNoPage number for command log pagination, from 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / fromdate / description
      Previous value: -"Filter builds from this date (YYYY-MM-DD)"New value: +"Filter builds from this date (YYYY-MM-DD, a real calendar date)"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return (pagination)"New value: +"Number of results to return, 1 to 100"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • 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: -"Offset for pagination"New value: +"Offset for pagination; pass the next offset from a previous response"
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageNumber / description
      Previous value: -"Page number for command log pagination"New value: +"Page number for command log pagination, from 1"
    • addedInput schema / properties / pageNumber / minimum
      Added value: +1
    • changedInput schema / properties / pageNumber / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Session ID — required for app platform log retrieval"New value: +"Session ID: required for session get and for app platform log retrieval. Session get also accepts the test ID instead."
    • changedInput schema / properties / todate / description
      Previous value: -"Filter builds to this date (YYYY-MM-DD)"New value: +"Filter builds to this date (YYYY-MM-DD, not before fromdate)"
  2. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"The action to perform on the resource"New value: +"The read to perform: list, or get one"
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "get",
      -  "delete",
      -  "update",
      -  "stop"
      -]New value: +[
      +  "list",
      +  "get"
      +]
    • changedInput schema / properties / buildId / description
      Previous value: -"Build ID — required for build get/delete/update/stop and optional for session list"New value: +"Build ID — required for build get, optional filter for session list"
    • removedInput schema / properties / name
      Removed value: -{
      -  "description": "New name for build update",
      -  "type": "string"
      -}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description still adds genuinely non-obvious behavior: the pagination object is authoritative and result_set.total overcounts stale builds, and logType "instrumentation" yields XCUI/Espresso output specifically. It stops short of error behavior or any limits on log retrieval volume.

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?

Four dense sentences, front-loaded with the capability inventory before the caveats and the sibling exclusions. The pagination warning and the logType note each earn their place; nothing is repeated from the schema or the annotations.

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 a 14-parameter, 4-resource matrix tool with no output schema, the description covers the combination space, pagination semantics, log types and sibling boundaries. It leaves the cross-field requiredness (which ID each get needs) entirely to the schema, and says nothing about failure or empty-result behavior.

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 the per-parameter semantics (testId, buildId, sessionId, logType, fromdate/todate, pageNumber) are already fully documented and the baseline is 3. The description reinforces the resource/action/platform matrix and adds the pagination-trust caveat, but it does not add syntax or constraint detail beyond the schema for individual fields.

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?

States a specific verb (read-only query) plus an enumerated resource set (builds, sessions, tests, logs) and explicitly says every combination works on platform "web" or "app". It also names the mutation siblings (updateBuild, stopBuild, deleteBuild) it is not, so an agent can separate it from those without opening any schema.

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?

Explicit when-not guidance is given for the mutation tools: renaming, stopping and deleting builds belong to updateBuild/stopBuild/deleteBuild. However, the description is silent about the heavily overlapping read siblings (getAutomationTestCommandLogs, getAutomationTestNetworkLogs, getAutomationTestSeleniumLogs, getAutomationTestBrowserConsoleLogs, getAutomationTestDetails), which cover the same logs/test data — an agent has no rule for choosing between them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources