Skip to main content
Glama

edit_block

Create, update, reorder, or configure a block. Use create without block_id to add a block. To remove one, use delete_block instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "edit_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew block name
createNoCreate a new block in a survey (omit block_id)
block_idNoBlock UUID. Omit when using create.
configurationNoBlock-kind configuration patch — use get_mcp_schema module=block kind=<block_kind>
reorder_in_surveyNoReplace the survey's block order (works on its own, without block_id). Only for a linear Flow: if the Flow has branches, randomizers, or Logic Splits it is refused rather than erasing them, and edit_flow flow_block_order changes the order instead.
restore_from_trashNoRestore one recoverable block, with its questions, from the survey's trash

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this is a mutating, non-destructive, non-idempotent operation, so the baseline burden is lower. The description adds the mode-selection rule (create without block_id) but says nothing about what an update overwrites, whether omitted fields are preserved, or that reorder replaces the entire order and can be refused on branched Flows — all of which live in the schema, not the prose.

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, zero filler, with the primary capability stated first and the exclusion routing second. Nothing can be trimmed without losing routing information.

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?

Output schema and annotations are present, so return values and safety profile need no prose. For a six-parameter, multi-mode tool the description covers the main modes and the delete alternative, but omits the trash-restore mode and the Flow-branching caveat on reorder, which an agent would only find by reading the schema.

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% and the nested `create`, `configuration`, and `reorder_in_survey` objects are richly documented, so the baseline is 3. The description's cross-parameter rule (create without block_id) largely restates what the schema already states in the `create` and `block_id` descriptions, and it never mentions the `restore_from_trash` parameter at all.

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?

Names a specific resource (block) and enumerates the operation set verb+resource style: create, update, reorder, configure. It explicitly carves out the removal case to a named sibling (delete_block), so an agent can separate it from delete_block without opening a schema.

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 concrete routing rules: use `create` without `block_id` to add, and use delete_block to remove. It does not distinguish update vs. reorder vs. restore modes, and the alternative for reordering a branching Flow (edit_flow) only appears in the schema, not in the description.

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