On this page

Agents

delete-agent

Can be held for approval

Delete an agent from the project's agent registry by its agent_id. Needs the fabric:orchestrate.write grant.

curl -sS -X POST https://fabric.wexa.ai/mcp/$FABRIC_PROJECT_ID \
  -H "authorization: Bearer $FABRIC_API_KEY" \
  -H "Mcp-Session-Id: $MCP_SESSION_ID" \
  -H "content-type: application/json" -H "accept: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"delete-agent","arguments":{"agent_id":"6ab196817566f41b5c28e335.6ab19681c73ec18cad7c9c48"}}}'
{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000208\",\"result\":{\"agent_id\":\"6ab196817566f41b5c28e335.6ab19681c73ec18cad7c9c48\",\"container_remains\":false,\"deleted\":true}}"
    }
  ],
  "isError": false
}

Parameters

ParameterTypeRequiredNotes
agent_idstringRequiredAgent id from list-agents or create-agent. An agent in this project.
Show full response

A real response, captured from a live call to delete-agent:

{
  "content": [
    {
      "type": "text",
      "text": "{\"lifecycle_id\":\"qlc_000208\",\"result\":{\"agent_id\":\"6ab196817566f41b5c28e335.6ab19681c73ec18cad7c9c48\",\"container_remains\":false,\"deleted\":true}}"
    }
  ],
  "isError": false
}
More details

Afterwards get-agent on that id reports not found. The container the agent was stored in goes with it, so nothing is left behind and no second call is needed. If that part fails the result carries container_remains: true, and delete-process-flow removes it. For a multi-agent process flow use the process-flow tools instead.

Every tool call works the same way: How every tool call works.