Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

WordPress: move a page section

wp_carbon_fields_move_row
Destructive

Move one section row of a Carbon Fields page to another position (e.g. the call to action to the top), or one item inside a section (a tab: pass parent). Previews the order before and after; confirm to move. The old order is backed up on the site and the page cache is cleared. Needs Bridge 1.7.0+.

Input Schema

NameRequiredDescriptionDefault
toYesThe new position
siteYes
fieldYesThe complex field, e.g. _crb_page_builder_sections (from wp_carbon_fields_get)
indexYesThe row, from wp_carbon_fields_get. For an item inside a section (a field index like 1:4, e.g. one tab), the second number
nestedNoOnly when that section has several nested lists: which one (e.g. tabs); the refusal names them
parentNoFor an item inside a section (index 1:4): the section row, the first number. Leave out for a whole section. Needs Bridge 1.7.1+
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / index / description
      Previous value: -"The row, from wp_carbon_fields_get"New value: +"The row, from wp_carbon_fields_get. For an item inside a section (a field index like 1:4, e.g. one tab), the second number"
    • addedInput schema / properties / nested
      Added value: +{
+  "description": "Only when that section has several nested lists: which one (e.g. tabs); the refusal names them",
+  "type": "string"
+}
    • addedInput schema / properties / parent
      Added value: +{
+  "description": "For an item inside a section (index 1:4): the section row, the first number. Leave out for a whole section. Needs Bridge 1.7.1+",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint the annotations already declare: it promises a before/after preview, gates the mutation on confirm, discloses that the old order is backed up and the page cache cleared, and states the Bridge version requirement. That is exactly the operational context an agent needs for a destructive tool.

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?

Four tight sentences, front-loaded with the operation, then the preview/confirm contract, then side effects and version requirement. No filler.

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

Completeness5/5

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

For a destructive move tool with no output schema, the description carries everything: both move modes, the preview payload, confirmation, backup, cache clearing, and version dependency. An agent can call it safely without further context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, so the schema already documents most parameters. The description adds cross-parameter meaning: parent pairs with the index for tab-level moves and is omitted for whole-section moves, and nested applies only when a section has several lists. Minor gap on post_id/site, which are undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('move one section row of a Carbon Fields page') and explicitly covers the second mode ('one item inside a section'). The example (call to action to the top) makes the operation concrete, and the reference to wp_carbon_fields_get anchors it to its sibling.

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

Usage Guidelines4/5

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

Explains the preview-then-confirm workflow and when to pass parent vs. leave it out for a whole section. It does not name when to prefer wp_carbon_fields_copy_row or wp_carbon_fields_remove_row instead, so alternatives are left to inference.

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

All Agency Autopilot 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