Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_move_block

Destructive

Moves an existing Gutenberg block to a different index within the same post.

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>",
      "post_id": "<post_id>",
      "to_index": "<to_index>"
    },
    "name": "wp_move_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post ID containing the block.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
to_indexYesZero-based destination block index.
from_pathNoRaw source path returned by wp_list_blocks.
from_indexNoZero-based source block index.
to_parent_pathNoRaw destination parent path. Omit for the top level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered, but the description adds almost nothing beyond the name: it doesn't say that sibling indices shift, whether content is preserved, what happens on an out-of-range destination, or how from_path and from_index interact. For a destructive reorder operation with two alternative source specifiers, that is a meaningful gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is part of why behavioral and usage gaps remain.

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

Completeness2/5

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

For a six-parameter, non-idempotent, destructive move tool with no output schema, the description is too thin: it leaves the from_path/from_index ambiguity unexplained and says nothing about index shifting, failure modes, or cross-post restrictions beyond 'same post'. An agent could still call it from the schema, but it lacks the context needed to call it correctly in edge cases.

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%, so every parameter is already documented, which sets the baseline at 3. The description adds no clarification of the ambiguous relationship between from_path and from_index (are they alternatives? must both be supplied?), so it does not exceed the baseline.

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 (Moves) and resource (existing Gutenberg block) plus a scope constraint ('within the same post'), which is enough to distinguish it from insertion/update tools at a glance. It does not explicitly contrast itself with siblings like wp_move_widget or wp_elementor_move_element, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (the schema alone says to call list_sites first), and no statement of when to prefer this over wp_update_block, wp_insert_block, or the Elementor move tool. The only constraint given is 'within the same post', which is a scope limit rather than selection guidance.

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

All Frontman for WordPress 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