Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by leonardobora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_set_blocksy_page_layout

Set a Blocksy page's sidebar to right, left, or none, using optional companion and dry-run to preview before writing.

Instructions

Set a Blocksy page to a right sidebar, left sidebar, or no sidebar through the optional companion. Reads the current protected page option and supports dry-run.

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": {
      "page_id": "<page_id>",
      "sidebar": "<sidebar>"
    },
    "name": "wp_set_blocksy_page_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview changes without writing
page_idYes
sidebarYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It does disclose useful behavior: it reads the current protected page option and supports dry-run. However, it does not clarify the 'optional companion' dependency, permissions, failure modes, or side effects of writing the layout.

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?

The description is concise and front-loaded with the main purpose. The second sentence adds behavioral value. The phrase 'optional companion' is vague but does not add length; the overall structure is efficient.

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 mutation tool with no annotations and no output schema, this description is under-specified. It does not explain the 'optional companion' requirement, what the tool returns, how to confirm the change, or when this should be used instead of other page tools. The dry-run mention helps but is not enough.

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 only 33%, so the description must compensate. It does partially: it explains sidebar values (right, left, no sidebar) and connects the action to a page. However, page_id and the dry-run behavior are not explained beyond the schema, leaving a meaningful gap.

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 clearly states a specific action and resource: setting a Blocksy page's sidebar layout to right, left, or none. It is distinct from the sibling tools, though it does not explicitly differentiate itself from alternative page-modification tools.

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?

No guidance is given about when to use this tool versus alternatives like wp_update_page, wp_get_page, or wp_list_sidebars. There are no contextual triggers, exclusions, or fallback instructions.

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