Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getTestsForBuild

Retrieves all tests associated with a specific build ID, enabling you to review test results and status for that build.

Instructions

Get all tests associated with a specific build ID.

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": {
      "buildId": "<buildId>"
    },
    "name": "getTestsForBuild"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildIdYesThe build ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden; it only conveys that this is a retrieval by build ID. It says nothing about result volume, pagination, ordering, or what happens when the build ID is unknown or invalid — meaningful gaps for a list endpoint.

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?

A single front-loaded sentence with no redundant wording; the resource and the scoping constraint appear immediately.

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 one-parameter read tool with no output schema and no nested objects, the description is minimally sufficient to call it correctly. It nonetheless leaves the meaning of 'tests' and the shape of the response undefined, which a slightly longer description could have covered.

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% for the single buildId parameter, so the schema already defines its meaning. The description only restates that the ID identifies a specific build, adding no format, type, or sourcing detail beyond 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?

States a specific verb and resource (get tests) plus scope (associated with a specific build ID), which lets an agent distinguish it from the broader getTests and from getTestDetails. The ambiguity is that 'tests' is not qualified, despite siblings like getAccessibilityTests and getVisualTests that partition test types.

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?

The phrase 'for a specific build ID' implies the filtering condition, but there is no explicit when-to-use guidance and no named alternative for retrieving tests by other dimensions. An agent must infer the routing itself.

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