Remove a specific step from a SendHustle automation by providing the automation ID and step ID. Disable the automation first if it's active to prevent errors during deletion.
Delete a step from an automation (DELETE /automations/:id/steps/:stepId). Stop (disable) the automation first if it is enabled.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The automation id. | |
| step_id | Yes | The step id to delete. |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses the DELETE method and the important stop-first requirement, but it does not mention irreversibility, required permissions, or what happens if the step is in use.
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?
The description is a single, front-loaded sentence that conveys the action, endpoint, and critical usage warning without any wasted words.
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 simple two-parameter delete operation, the description is largely complete: it identifies the action, endpoint, and precondition. It does not describe the response or side effects, but the operation's simplicity makes this a minor gap.
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 coverage is 100%, and the two parameters are clearly documented as 'automation id' and 'step id to delete'. The description adds no new parameter semantics beyond confirming the endpoint mapping.
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?
The description states a specific verb and resource: 'Delete a step from an automation', and reinforces it with the HTTP endpoint. This clearly distinguishes it from siblings like delete_automation, add_automation_step, and update_automation_step.
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?
The description gives an explicit precondition: 'Stop (disable) the automation first if it is enabled.' It does not explicitly compare to alternatives, but the resource is specific enough that when to use it is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.