JavaScript
Tool Sets
Update a tool set
Change the name, labels, or adapter. Editing the adapter is also how you force a re-sync.
PATCH
JavaScript
Change a tool set after it exists: rename it, relabel it, or edit the adapter. Any update also triggers a re-sync, so this is how you refresh a set on demand.
So you do not have to resend the whole adapter to change a label, and omitting your filters does not wipe them.
Verified: seconds after this patch, the matching tool flips to
The update merges
Send one field and the rest survive. A name-only patch keeps the adapter and the labels untouched:Any update re-syncs
There is no sync endpoint. Cadenya syncs on create and on every update. So the way to force a refresh, pick up a provider’s new tools, or reapply a filter, is toPATCH the set, most naturally by resending the adapter.
STATE_OMITTED and the event log shows a fresh syncStarted / syncCompleted.
Send the adapter whole, with its
type discriminator and the full variant payload. When you re-sync to reapply a filter, include the url (or baseUrl) alongside the filter, as above, rather than sending the filter alone.Curate a synced set here, not on its tools
A synced tool set does not let you edit its individual tools (:omit is transient there). The durable curation is includeTools / excludeTools on the adapter, set through this endpoint. A filter is reapplied on every sync, so it sticks where a per-tool omit does not.
Related
Create a tool set
The adapter kinds and the filter grammar in full.
List tool set events
The
syncStarted an adapter edit produces.Omit a tool
Why per-tool omit does not survive on a synced set.
Archive a tool set
Stop syncing entirely, reversibly.
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"
Body
application/json
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