Set tool endpoint
Update an HTTP tool's method + URL (always together, they're coupled). Identify the tool by toolName (its snake_case name) or toolId. URL may contain `{{variable_name}}` placeholders.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/set_tool_endpoint" \ -H "Content-Type: application/json" \ -d '{ "method": "GET", "url": "string", "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Edit tool description POST
Update an existing tool's `description` and/or `displayName`. Identify the tool by toolName (its snake_case name) or toolId. The description is the highest-leverage prompt surface, the LLM reads it every turn. Most behaviour tweaks ('only call this after the caller has confirmed their phone', 'falls back to email if SMS fails') belong here, not in the system prompt.
Set tool follow-up POST
Decide what happens when a call ends before this tool fires, the caller hangs up mid-enquiry and the action the agent was working toward is lost. `off` (default) loses it, as today. `notify` has a post-call judge read the call and alert someone with what the agent was about to do. `complete` runs the tool after the call through a headless agent-run, using only what the caller actually said, then reports that it ran. `complete` is refused on tools that need the live call (transfer_to_human, end_call, the live-screen set) or that message the CALLER rather than the business (send_text_message), use `notify` for those. Set `requiredArgs` so a half-finished call downgrades to notify instead of guessing a phone number, and `note` to tell the judge when NOT to act (cold callers, robocalls). Identify the tool by toolName or toolId.