Delete an agent tool
Removes a tool from the agent. The row is soft-deleted (it disappears from every read and its name becomes available again) and the agent’s remaining tools are pushed to the voice provider, so the model can no longer call it from the next conversation on. Conversations already in progress keep the configuration they started with.
Side effects. Updates the agent in the voice engine. If that push fails, the tool is restored
and the request answers 500. If a workflow phase references the tool through toolIds,
update the workflow too (PUT /api/agents/{agentId}/workflow). The mutation is written to
the audit log.
Idempotency. Safe to retry: a repeat on an already deleted tool answers
404 TOOL_NOT_FOUND.
Webhook events. audit.log_recorded for endpoints subscribed to it. See Webhooks.
Access
- Required scope:
write. - Rate limit: Configuration mutations — 10 requests/min per workspace, shared with other agent configuration writes, in addition to the General API limit. See Rate limits.
- Plan: Available on every plan.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.