Skip to main content
GET
JavaScript
Every agent variation with the tool set assigned, each row carrying the variation, its parent agent, and its model. Read it before you delete or archive a set, so the blast radius is a list instead of a surprise.

Filter down to one tool

Pass toolId to list only the variations with a direct assignment of that individual tool. The tool must belong to the set. Variations that receive the tool implicitly, through a whole-set assignment, do not appear in the filtered view. So the two reads answer different questions: no filter answers “who uses this set”, and the filter answers “who asked for this specific tool by name”.

What a row carries

Each ToolSetUsage row holds three metadata blocks (agentVariation, agent, model) and assignedAt, the moment the assignment was created. sortOrder sorts by that timestamp, and limit and cursor page the results the usual way.

Delete a tool set

What this list protects you from.

Add an assignment

Where the rows here come from.

List tool sets

The sets themselves, with live tool counts.

Prevent tool bloat

Why assignments should stay deliberate.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

Workspace ID.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

toolSetId
string
required

Tool set ID. Accepts the canonical ts_… form or the external_id: form.

Example:

"toolset_01HXKD2E5NQM3T9AYWCFNRMN74"

Query Parameters

toolId
string

When set, lists only variations with a direct assignment of this individual tool. When unset, lists variations assigned the whole tool set. The tool must belong to the tool set.

Example:

"tool_01HXKD2E5NQM3T9AYWCFWVYY9K"

limit
integer<int32>

Maximum number of results to return

cursor
string

Pagination cursor from previous response

sortOrder
string

Sort order for results (asc or desc by assignment creation time)

Response

OK

items
object[]
pagination
object

Page carries cursor-based pagination state. There is no total: the cursor walks the result set without ever counting it, and a count would cost a second query on every list.