Skip to main content
Glama

Reorder Blocks

reorder_blocks
DestructiveIdempotent

Reorder blocks on a page. Provide the complete list of block IDs in the desired order.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Replaces the order of a page's sections on the DRAFT — a non-additive update, so destructive by the MCP definition; idempotent; closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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": {
      "site_id": "<site_id>",
      "page_slug": "<page_slug>",
      "block_ids": "<block_ids>"
    },
    "name": "reorder_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
block_idsYesOrdered list of ALL block IDs for this page
page_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The rationale adds genuinely new context beyond the annotations: the change is draft-scoped and the live site only changes on publish_site confirmation. However, much of the paragraph restates the annotations verbatim (destructive because non-additive, idempotent, closed-world), and it never says what happens if the list is incomplete, contains unknown IDs, or omits existing blocks.

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

Conciseness3/5

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

The operational sentence is front-loaded and efficient, but the appended rationale paragraph is long and partly duplicates the annotation flags word-for-word, diluting the high-value draft-vs-live point.

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

Completeness3/5

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

For a destructive, idempotent mutation the definition covers scope and publish gating, but with no output schema and only partial parameter documentation, an agent still lacks error/edge-case behavior (invalid or incomplete block lists) and confirmation of what the call returns.

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 only 33% — site_id and page_slug are undocumented in both schema and description. The description reinforces block_ids semantics ('complete list' and 'desired order', implying replacement rather than patching), which is useful, but it does not compensate for the two unexplained parameters.

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?

The description names a specific verb and resource ('Reorder blocks on a page') and states the required input shape ('complete list of block IDs in the desired order'), so an agent can distinguish it from add_block, remove_block, and update_block. It stops short of explicitly contrasting itself with those siblings.

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?

It gives a clear precondition ('provide the complete list of block IDs') and clarifies the operating context: changes land on the DRAFT and only reach the live site via publish_site. There are no explicit exclusions or named alternatives for when a partial reorder should be done differently.

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.