List available tools
List every capability and in-call tool an agent can install, in one catalog.
Capabilities bundle an in-call action with its supported settings and related behavior. Capabilities and tools are both installed and set up with PATCH /api/agent-builder/agents/{id}/campaign, in the field the table names.
| Catalog entry | Kind | Campaign field |
|---|---|---|
| Appointment Booking | Capability | capabilities.appointment_booking |
| Service Area Check | Tool | tools.smart_service_area |
| Live Transfer | Capability | capabilities.live_transfer |
| Add a Tag | Capability | capabilities.add_tag |
| Check a Tag | Tool | tools.check_tag |
This catalog lists what is available, not what is installed. To see what a campaign has installed, call GET /api/agent-builder/agents/{id}/campaign and read capabilities and tools. A campaign may have zero capabilities. To install an entry, call PATCH /api/agent-builder/agents/{id}/campaign with enabled: true and its required settings in the field the table names. Omitted entries stay unchanged, and null removes one. To refuse the change when the installed entries changed since you read them, send campaign.metadata.inventoryVersion from that read as expectedVersion. The settings each entry takes are in the request schema of PATCH /api/agent-builder/agents/{id}/campaign. To change one skill, use PATCH /api/agent-builder/agents/{id}/skills/{skillId}.
The catalog name is a display label, such as “Live Transfer”. It is not the toolName that PATCH /api/agent-builder/agents/{id}/tools takes. To find that name, call GET /api/agent-builder/agents/{id}?view=tools and copy the exact installed tools[].name, such as transfer_call. A single catalog entry can create multiple installed tools. To add a custom plain-English skill, use POST /api/agent-builder/agents/{id}/skills with type: "instructions".
Required API key scope: agents:read.
