Skip to main content
POST
JavaScript
The inverse of :omit. A tool in STATE_OMITTED returns to STATE_AVAILABLE, and agents see it again on their next objective.
Idempotent: restoring an already-available tool is a 200 no-op.

Scope, by tool set kind

:restore undoes a manual :omit, so it fits the same tool sets :omit does: bare and HTTP sets, where you author the tools by hand. On a synced (mcp or openapi) set, the tool’s state is decided by the source and the adapter filters. A tool hidden by excludeTools cannot be brought back with :restore; it returns the moment you drop it from the filter and the set re-syncs.
On a synced set, :restore returns 200, but a tool’s availability there is governed by the sync, not by this call. Use the adapter filters to curate a synced set.

Omit a tool

Hide a tool. The action this reverses.

Create a tool set

includeTools and excludeTools, the durable curation for synced sets.

List tools

Confirm the state after a restore.

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"

id
string
required

Tool ID. Accepts the canonical tool_… form or the external_id: form.

Example:

"tool_01HXKD2E5NQM3T9AYWCFWVYY9K"

Body

application/json

Restore tool request

Response

OK

metadata
object
required

Standard metadata for persistent, named resources (e.g., agents, tools, prompts)

spec
object
required
state
enum<string>
required
read-only

The current lifecycle state of the tool. Output only. Use the :omit and :restore actions to transition; tool set syncs may also update it.

Available options:
STATE_UNSPECIFIED,
STATE_AVAILABLE,
STATE_OMITTED,
STATE_ARCHIVED
info
object