Frontman for WordPress

wp_move_widget

Destructive

Moves a widget to a different sidebar or position, or restores a removed widget using its retained instance ID.

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>",
      "widget_id": "<widget_id>",
      "to_sidebar_id": "<to_sidebar_id>"
    },
    "name": "wp_move_widget"
  }
}

Input Schema

Name	Required	Description
`site_id`	Yes	The connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
`widget_id`	Yes	The widget instance ID to move.
`to_position`	No	Optional 1-based position in the destination sidebar.
`to_sidebar_id`	Yes	Destination sidebar ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already mark this as destructive and non-idempotent, but the description adds that a removed widget can be restored via its retained instance ID, which is meaningful behavior beyond the annotations. It still does not explain side effects on the original sidebar or permission requirements, but with annotations present this is a useful addition.

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?

The description is a single front-loaded sentence that covers both move and restore without filler. Every clause contributes directly to understanding the operation.

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?

The schema fully documents parameters and annotations cover the safety profile, while the description covers both operational modes. However, for a destructive mutation tool it omits details such as destination-position collision handling and permission requirements, leaving clear gaps.

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 documents all four parameters, so the baseline is 3. The description only reinforces that widget_id is the retained instance ID for restoration, adding little beyond what the schema already says.

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 the specific action (moves) and resource (widget), and adds the non-obvious restoration mode using a retained instance ID. It does not name a sibling alternative, so it is clear but not fully differentiated from related tools such as wp_update_widget.

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

Usage Guidelines3/5

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

It implies when to use the tool by describing moving and restoring, but gives no explicit when-not conditions or alternatives such as using wp_update_widget for renaming or wp_delete_widget for removal. The agent must infer the boundaries.

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 tools Inspect

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.