2b2t Atlas

get_group_builds

Read-only

Page through a group's builds in stable name/ID order. Pass offset=0 initially, then advance by the returned count until a short page. get_group supplies the total count and first 20 builds. Prefer interactiveUrl for human links and citations. recordUrl is a stable provenance alias with a permanent HTTP 301 redirect to the interactive HTML. Use apiUrl or JSONL for JSON. Derivatives use locationInteractiveUrl/locationRecordUrl.

Input Schema

Name	Required	Description
`limit`	No	Maximum results, from 1 to 100. Defaults to 50.
`offset`	No	Zero-based result offset. Defaults to 0; must be non-negative.
`group_id`	Yes	Persistent numeric Atlas group ID.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- changedOutput schema / properties / result / items / properties / y / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```
Changed1 schema field changedSep 28, 2026
- addedOutput schema / properties / result / items / properties / recordUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based result offset. Defaults to 0; must be non-negative.",
+  "type": "integer"
+}

First observedSep 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the read-only/non-destructive safety profile; the description adds the pagination termination rule, the redirect behavior of recordUrl (permanent HTTP 301 to interactive HTML), and which field to use for machine-readable output (apiUrl or JSONL). It also clarifies that derivative entities use different URL fields (locationInteractiveUrl/locationRecordUrl), which an agent could easily get wrong.

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, each with a distinct payload: pagination procedure, sibling relationship, URL selection, and derivative-field caveat. The call procedure is front-loaded and there is no filler.

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?

An output schema exists, yet the description still adds the interpretive guidance an agent needs (which URL field for humans vs. JSON vs. derivatives) without duplicating field-by-field return docs. For a paged read tool with three simple params, nothing required for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real semantics beyond the schema: offset should start at 0 and advance by the returned count, and iteration stops on a short page. It does not restate the 1-100 limit bound, which the schema already carries.

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 and resource ('Page through a group's builds') plus the ordering guarantee ('stable name/ID order'). It also explicitly separates itself from the sibling get_group, which 'supplies the total count and first 20 builds', so an agent can route between the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit call procedure ('Pass offset=0 initially, then advance by the returned count until a short page') and states the alternative path (get_group for totals and the first page). When-to-use, how-to-iterate, and the alternative are all named.

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

All 2b2t Atlas tools Inspect

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.