Skip to main content
Glama

delete_block

DestructiveIdempotent

Remove a block from active survey content, with confirm: true. Moves the block and its questions to recoverable survey trash — restore with edit_block.restore_from_trash.

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": {
      "block_id": "<block_id>",
      "confirm": "<confirm>"
    },
    "name": "delete_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. The block and its questions move to recoverable survey trash, not permanent deletion — but require explicit confirmation before removing them from the active survey.
block_idYesBlock UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the blast radius (the block and its questions move together), that the operation is recoverable rather than permanent, and the exact restore tool. With destructiveHint=true already flagged, this adds the operational detail an agent actually needs before committing.

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

Conciseness4/5

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

Two tight sentences, front-loaded with the action and then the consequence/recovery. Only mild redundancy with the schema's confirm description, which repeats the trash explanation almost verbatim.

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?

Complete relative to complexity: a destructive two-parameter tool with full schema coverage, an output schema, and rich annotations. Side effects, confirmation requirement, and restoration are all covered, leaving nothing essential for a correct call 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?

Schema coverage is 100% and the confirm boolean already documents "Must be true" plus the trash semantics, so the description is largely restating structured data. Baseline 3 applies since the schema carries parameter meaning on its own.

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+resource: "Remove a block from active survey content." The resource (block) plus the scope qualifier (active survey content) separates it cleanly from the many delete_* siblings that act on questions, comments, flows, or responses.

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?

Gives an explicit prerequisite ("with confirm: true") and names the recovery path via edit_block.restore_from_trash, so an agent knows the follow-up tool after acting. It stops short of stating when not to use it, e.g. versus deleting a question inside a block or restoring from trash instead of deleting, so it is clear context but not a full decision tree.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources