Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

Delete agent

delete_agent

DestructiveIdempotent

Permanently delete an agent and revoke its disk. This cannot be undone; built workflows stay in the account, but live ones pause until reassigned.

Instructions

Permanently delete an agent and revoke its disk. This cannot be undone. Workflows the agent built are NOT deleted — they belong to the account — but the ones that were live are paused, and none of them run again until you assign them to another agent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent's UUID to delete.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes	The successful HTTP status code from the underlying operation.
`workflows_paused`	No	How many workflows this agent had built and had running were paused by the deletion. They are not deleted: assign them to another agent to run them again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "status": {
+      "description": "The successful HTTP status code from the underlying operation.",
+      "type": "integer"
+    },
+    "workflows_paused": {
+      "description": "How many workflows this agent had built and had running were paused by the deletion. They are not deleted: assign them to another agent to run them again.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 4, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only flag destructiveHint and idempotentHint; the description goes well beyond that by disclosing irreversibility ('cannot be undone'), the side effect on the agent's disk, and the precise blast radius for workflows — not deleted, live ones paused, blocked until reassigned. That is exactly the context an agent needs before committing an irreversible action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action and the irreversibility warning before the workflow nuance. Every sentence carries distinct, decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the description covers the action, reversibility, and cross-entity side effects. Nothing needed to call this destructive tool safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter and schema coverage is 100%, so the schema already fully documents agent_id as the UUID to delete. The description adds no format or sourcing detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Permanently delete an agent') plus a secondary effect ('revoke its disk'), which cleanly separates it from read/list siblings like get_agent and list_agents and from cancel_run.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Consequences are well described, but there is no explicit guidance on when to delete versus alternatives such as cancel_run or reassigning the agent via set_workflow_agent. Usage is implied by the destructive framing rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.