Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_insert_block

Destructive

Inserts a new Gutenberg block into a post at a given position. Appends to end if index is omitted.

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>",
      "block_markup": "<block_markup>"
    },
    "name": "wp_insert_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoZero-based position to insert at. Appends to end if omitted.
post_idYesThe post ID to insert the block into.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
parent_pathNoRaw path of the parent block. Omit to insert at the top level.
block_markupYesThe block markup to insert (HTML with Gutenberg block comments).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare this a non-read-only, non-idempotent, destructive, open-world mutation, and the description adds essentially nothing beyond that profile. It does not say what happens to existing content at the target index, whether insertion can fail, or what the response contains. The only behavioral detail given, the append default, merely restates the schema.

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, front-loaded with the action and resource, with the fallback behavior stated second. Nothing is wasted and nothing important is buried.

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 five-parameter destructive mutation with no output schema, the definition covers the basic action and the index default but omits error behavior, permission requirements, and what the call returns. It is minimally adequate given the rich schema but not complete.

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 including site_id (with its 'call list_sites first' caveat), index, parent_path, and block_markup is already documented. The description repeats the index default rather than adding new meaning, so the baseline of 3 applies.

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 gives a specific verb and resource ('Inserts a new Gutenberg block into a post') plus a positional qualifier, so the agent knows exactly what operation is performed. It does not distinguish itself from siblings such as wp_update_block or wp_move_block, which is why 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 guidance on when to use this instead of wp_update_block, wp_move_block, or wp_read_block, and no prerequisites or exclusions are stated. The only conditional behavior mentioned ('Appends to end if index is omitted') is a default, not usage 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