Skip to main content
Glama

mcp_move_widget

Move a WordPress widget to another sidebar and optionally set its 0-based position to reorganize site layouts.

Instructions

Move a widget to a different sidebar

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": "<site>",
      "widget_id": "<widget_id>",
      "sidebar_id": "<sidebar_id>"
    },
    "name": "mcp_move_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
positionNo0-based position in the target sidebar (default: append at the end)
widget_idYesWidget ID
sidebar_idYesTarget sidebar ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • changedInput schema / properties / position / description
      Previous value: -"Position in target sidebar"New value: +"0-based position in the target sidebar (default: append at the end)"
    • addedInput schema / properties / position / minimum
      Added value: +0
    • changedInput schema / properties / position / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "widget_id",
      -  "sidebar_id"
      -]New value: +[
      +  "site",
      +  "widget_id",
      +  "sidebar_id"
      +]
  3. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description bears the full behavioral burden, and it discloses almost nothing beyond the basic effect. It does not say whether widget settings/content are preserved across the move, what happens to sibling widgets' ordering, whether the operation is idempotent when the widget is already in the target sidebar, or what permissions are required for a mutation.

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 nine-word sentence with no filler, and the core action is front-loaded. Its brevity is efficient rather than padded, though it shades into under-specification given the mutation context.

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 an unannotated mutation tool with no output schema and four parameters, the description is far too thin: an agent gets no information about side effects, preserved state, ordering behavior, or success/failure signals. Rendering the destination sidebar well enough to call the tool is possible from the schema, but understanding the consequences is not.

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 all four parameters (site, widget_id, sidebar_id, position) are already documented in the schema, including the append-by-default semantics of position. The description adds no parameter-level meaning beyond that, making 3 the appropriate 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?

The description gives a specific verb and resource ("Move a widget") plus the destination scope ("different sidebar"), which is clearer than a bare restatement of the name. It does not, however, distinguish this from sibling mcp_update_widget, which may plausibly also change a widget's sidebar assignment, so an agent cannot route with confidence from the description alone.

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 or when-not-to-use guidance, and no mention of prerequisites such as whether the widget must already exist or whether the target sidebar must exist. The most important routing question — move vs. mcp_update_widget — is left entirely unaddressed.

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

Deploy Server

Other Tools