Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

WordPress: copy a page section

wp_carbon_fields_copy_row
Destructive

Copy one section row of a Carbon Fields page to the end of the page, or one item inside a section to the end of that section (pass parent) (to then change its text with wp_replace_in_post, e.g. a new tab or service block). Previews first; confirm to copy. Needs Bridge 1.7.0+.

Input Schema

NameRequiredDescriptionDefault
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/5.0
Behavior4/5

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

Annotations already declare this as destructive, non-idempotent, and non-read-only, and the description adds useful behavior: the copy is appended to the end, a preview is shown first, and confirmation is required. It also names the minimum Bridge version, though it does not fully describe the resulting side effects.

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 front-loaded with the core copy behavior, then gives the parent case, workflow note, and version requirement in three sentences. There is no redundant or filler text.

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

Completeness4/5

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

It covers the main purpose, the nested-section parent case, preview/confirm behavior, and a version prerequisite. For a seven-parameter destructive mutation with no output schema, it is mostly complete, though it could say more about expected preview output or failure/refusal behavior.

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 coverage is 71% and already documents most parameters in detail. The description adds the key semantic that parent is passed when copying an item inside a section, but it does not clarify all parameters such as site, post_id, or the preview/confirm response behavior beyond the schema.

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 states a specific verb and resource: copying one Carbon Fields section row to the end of the page, or one item to the end of its section. It is clear, but it does not explicitly distinguish the operation from nearby siblings such as wp_carbon_fields_move_row or wp_carbon_fields_remove_row.

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?

It explains the intended workflow: copy a row or item, then optionally change its text with wp_replace_in_post. It also states that a preview happens first and confirm is needed to copy, but it does not explicitly exclude or compare against move/remove alternatives.

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