Skip to main content
Glama
Sign In

Agency Autopilot

by com.jiyumarketing.mcp
OverviewDiscussionsAdmin

WordPress: remove a page section

wp_carbon_fields_remove_row
Destructive

Remove one section row from a Carbon Fields page, or one item inside a section (a tab such as "Tiny Home Construction" at 1:4: parent 1, index 4). Previews the sections before and after; confirm to remove. The removed row is backed up on the site. 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.2/5.0
Behavior4/5

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

Annotations already declare the tool destructive, but the description adds important context: it previews sections before and after, requires confirm, backs up the removed row, and depends on Bridge 1.7.0+. It does not cover permissions or failure behavior, but the key safety traits are disclosed.

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 tightly written sentences with the primary action and scope front-loaded. Each sentence adds useful information about nesting, preview, backup, or version requirements.

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?

For a destructive mutation with no output schema, the description explains the preview, backup, and version dependency well enough to call it correctly. It leaves out failure/refusal details, but those are partly covered by the schema's nested parameter description.

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 field, index, parent, nested, and confirm in detail. The description reinforces the nested index example and preview/confirm semantics but adds little syntax or meaning beyond the schema.

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: remove one section row from a Carbon Fields page or one item inside a section. The nested example clarifies exactly what is being removed, and the verb distinguishes it from the sibling copy and move row tools.

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 operational workflow: preview the before/after state, then set confirm to remove. It also notes the Bridge version requirement, but it does not explicitly name alternative tools or when not to use this one.

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