delete_approval_workflowRemove an approval workflow from LightCMS by its ID to stop or clean up an outdated review process. Provide the workflow ID to remove it.
Delete an approval workflow.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | required,Workflow ID to delete |
Changes observed during successful MCP inspections.
v7.3.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds nothing beyond that: no statement about irreversibility, whether in-flight approval requests are affected, or required permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. It is tight, though its brevity reflects under-specification rather than disciplined concision.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a destructive mutation with one required id and no output schema, the description omits the consequences an agent needs: irreversibility, effect on existing approval requests, and confirmation expectations. Annotations cover the destructive flag but not these operational details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single id parameter is documented in the schema as 'Workflow ID to delete'. Baseline 3 applies since the schema fully carries parameter detail and the description adds no additional format or syntax meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Delete) and resource (approval workflow), matching the title exactly. It does not differentiate from siblings like delete_template, delete_redirect, or delete_webhook, but the resource is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus alternatives such as update_approval_workflow or cancel_approval_request, and no prerequisites or warnings about when deletion is inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.