Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Delete block

delete-block-tool
Destructive

Remove a block from a form's draft. Only affects the draft — respondents see the change after publish-form-tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_slug": "<form_slug>",
      "block_id": "<block_id>"
    },
    "name": "delete-block-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRequired to be true to confirm removing a block that already has submission data (the tool returns has_data otherwise). Ask the user before forcing.
block_idYesThe id of the block to remove, from get-form-tool.
form_slugYesThe form's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the safety profile is known; the description still adds real value by disclosing that the removal is draft-scoped and only reaches respondents after a publish. It stops short of stating irreversibility or what happens to logic attached to a removed block.

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?

Two short sentences: the action and its scope come first, followed by the publish consequence. No redundant phrasing and nothing that restates the tool name.

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

Completeness4/5

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

For a destructive, fully-documented three-parameter tool, the description covers what changes and when it takes effect, while the schema covers the force confirmation. It could be stronger by noting that blocks with submission data are rejected without force, and whether the response includes a has_data flag.

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?

Schema description coverage is 100%, including the tricky force/has_data confirmation flow and where block_id comes from, so the schema carries the parameter burden. The description adds no parameter-level meaning beyond it, making the baseline 3 appropriate.

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

Purpose4/5

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

States a specific verb and resource ('Remove a block') plus a scoping qualifier ('from a form's draft'), which implicitly separates it from add-block-tool, update-block-tool and publish-form-tool. It does not name a sibling explicitly, so the differentiation is inferred rather than stated.

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?

The description clarifies when the effect of this tool becomes visible ('respondents see the change after publish-form-tool') but gives no when-to-use/when-not-to-use guidance relative to update-block-tool or add-block-tool. The 'ask the user before forcing' rule lives in the schema, not the description.

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

All Youform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources