Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getBuilds

Retrieve builds that group related tests, with optional limit and offset pagination to browse test history.

Instructions

Get a list of builds with optional pagination. Builds group related tests together.

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": "getBuilds"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of builds to retrieve (default: 10, max: 100)
offsetNoOffset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/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 disclosure burden. 'Get a list' implies a non-destructive read and pagination is described as optional, but there is no mention of ordering, result shape, empty results, permissions, or total-count behavior.

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 short sentences, front-loaded with the action and followed by the one domain fact needed to interpret 'build'. Nothing is wasted or redundant.

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 simple two-parameter list tool with a fully documented schema, this is close to adequate, but with no output schema the agent gets no sense of what a build record contains or how results are ordered, which the description could have supplied.

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 both limit and offset are already fully documented with defaults and bounds. The description's only added signal is that pagination is optional, which the schema's defaults already convey; baseline 3 applies.

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?

A specific verb and resource ('Get a list of builds') plus a domain clarification that builds group related tests. It is distinguishable from data-detail siblings such as getTestDetails or getTestsForBuild, though it doesn't explicitly contrast itself with them.

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: fetch builds when you need the build list. There is no explicit guidance on when to prefer this over getTestsForBuild or when a build id is needed instead, and no stated prerequisites.

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