JavaScript
Tool Sets
Get a tool set
One tool set: its adapter, its state, and the counts that tell you whether it is healthy.
GET
JavaScript
Read one tool set.
A secret referenced in an adapter header comes back as its
A missing ID is a
spec.adapter tells you what it points at, state whether it is active, and info how many tools it holds.
What the counts tell you
info returns on every read; includeInfo is a no-op on tool sets. Five fields, and the three counts are how you spot a problem without listing the tools:
availableTools short of toolCount means tools are omitted.
info.lastSync is documented on the tool set, but it is omitted until a sync completes successfully. A set whose syncs have only ever failed has no lastSync, so read the event log to see what happened rather than inferring health from its absence.The adapter is a union
spec.adapter carries a type of mcp, openapi, http, or bare, and the key matching type holds the payload. Switch on type to know the kind:
${NAME} placeholder, never resolved, so a read never leaks a credential.
Fetch by your own ID
Tool sets take an external ID:404.
Related
List tools
The tools this set holds, with their states.
List tool set events
Whether the last sync landed, when
lastSync cannot tell you.Create a tool set
The four adapter kinds in full.
Archive a tool set
The reversible retirement, allowed even while assigned.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Workspace ID.
Example:
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Tool set ID. Accepts the canonical ts_… form or the external_id: form.
Example:
"toolset_01HXKD2E5NQM3T9AYWCFNRMN74"
Response
OK
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
The current lifecycle state of the tool set. Output only. Tool sets are created STATE_ACTIVE; use the :archive and :unarchive actions to transition between states.
Available options:
STATE_UNSPECIFIED, STATE_ACTIVE, STATE_ARCHIVED Tool set information