asksteps

asksteps: delete a form and its submissions

asksteps_delete_form

Destructive

Deletes a form or funnel from the connected account — together with every submission it has collected. Requires "forms:write". The first call NEVER deletes: it returns "confirmation_required" and the number of submissions that would be lost. Read that number out to the user, get their agreement, and only then call again with confirm = true. This cannot be undone.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`confirm`	No	Set to true only AFTER the user has agreed, knowing how many submissions go with it.
`form_id`	Yes	The form or funnel id.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	One sentence for the user. On "confirmation_required" it says how many submissions would be lost — read that number out loud before asking.
`status`	Yes	Outcome. One of: "deleted", "confirmation_required" (read the note and call again with confirm = true if the user really wants this), "not_connected", "not_found", "error". Authorisation can also refuse before the tool runs: "plan_required" (the account's plan does not include agent access), "not_enabled" (the account owner has not switched agent access on), "owner_required" (only the account owner may do this), "mandate_required" (the owner has not granted a mandate for this). The note then says what the user has to do.
`leadCount`	No	How many submissions this form has collected. Deleting the form deletes them too.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true), the description discloses critical behavioral traits: the two-call confirmation protocol, the confirmation_required response with submission count, the permission requirement, and irreversibility ('This cannot be undone'). These details are not present in the annotations and add substantial safety-relevant context.

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 cover the action, prerequisite, the two-call protocol, and irreversibility. Every sentence earns its place; no filler or redundancy. The most critical safety detail (first call never deletes) is front-loaded after the action statement.

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?

Given the destructive nature and the output schema availability, the description fully covers the prerequisites, the required user-confirmation workflow, and the irreversible consequence. An agent has everything needed to invoke the tool correctly and safely.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds operational meaning to the confirm parameter by explaining the two-call sequence and when to set confirm to true, complementing the schema's own parameter description. form_id is straightforwardly covered by schema.

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?

The description uses a specific verb ('Deletes') and clearly identifies the resource ('a form or funnel from the connected account') along with the scope ('together with every submission it has collected'). This unambiguously distinguishes it from sibling tools like asksteps_update_form or asksteps_publish_form.

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

Usage Guidelines4/5

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

The description provides explicit operational guidance: requires 'forms:write', first call never deletes, must read the confirmation count to the user, and only call again with confirm = true. It does not explicitly name alternative tools or state when not to use it, but the delete context is clear enough that no closer alternative exists among siblings.

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

All asksteps tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Tools are mostly distinct with clear ownership of each resource and action, and descriptions explicitly contrast sibling pairs (analyze_pdf vs import_pdf, create_form vs create_funnel, publish_form vs update_publication, change_plan vs start_checkout). However, an agent skimming names alone could misselect between the four creation tools or the two PDF tools without reading the descriptions carefully.

Naming Consistency5/5

Every tool follows the asksteps_<verb>_<noun> pattern perfectly, with uniform verbs like get_, list_, create_, and update_. The only slight deviation is create_from_template, but even that stays predictable and readable within the convention.

Tool Count3/5

At 24 tools, this sits at the heavy end of the 16-25 borderline range. The broad domain (form/funnel building, publishing, PDF import, billing, stats, leads) justifies most of them and there is no obvious redundancy, but the sheer volume makes navigation harder than a tighter set.

Completeness4/5

The core form and funnel lifecycle is well covered: multiple creation paths, read, full replacement update, delete with confirmation, publish/unpublish, stats, and leads export. Billing covers first purchase, plan changes, and quota checks. Minor gaps exist — no dedicated subdomain listing tool, no funnel-specific stats, and no programmatic PDF field mapping — but these are explicitly documented as human steps, so agents can work around them.

Resources

Need Help?