nibwp/forms-manage

nibwp/forms-manage is a write ability in NIBWP’s forms toolset. Create or update forms data in a single typed call — fields, status and relationships set together, with force-draft so nothing goes live unreviewed. Like every NIBWP ability it is a typed MCP tool: the agent calls it by name with structured arguments, NIBWP validates those arguments against a schema, checks them against your token’s scopes, runs the operation, and records the call in the audit log. Nothing about it is a black box — you can see exactly what it accepts, what it returns, and what it did.

What forms-manage does

nibwp/forms-manage is a write ability: it creates or updates records, validates every argument against a schema, honors force-draft, and returns the affected ID so agents can chain the next step.

When to reach for it

Reach for nibwp/forms-manage whenever an agent needs to produce or change something in the forms area — drafting content, updating records, filling fields, or applying a change across many items at once. Because it is a write ability, it is the workhorse of content and data workflows: the step where the agent stops reading and starts doing. Pair it with a read ability first to find the right targets, then let it act on them in a controlled, reviewable batch.

How a call works

Every call to nibwp/forms-manage follows the same four-step path, which is what makes it safe to put in an agent’s hands:

• Validate — your arguments are checked against the tool’s JSON schema before anything runs.
• Authorize — the call is checked against your token’s scopes; out-of-scope calls are refused.
• Execute — the operation runs against WordPress through the standard, supported APIs.
• Audit — the call is logged with status, timing, the calling token and the result.

Parameters

The arguments nibwp/forms-manage accepts. Anything marked required must be present; optional arguments fall back to sensible defaults.

Walkthrough: a real call

Here is the shape of a typical request — what the agent sends when it decides to use this ability:

tool: "nibwp/forms-manage"
args: {
  data: { title: "Example" },
  status: "draft"
}

And the structured response it gets back, ready to chain into the next step:

200 { id: 512, status: "draft" }

What it can do

• Create or update records in one typed call
• Set fields, status and taxonomies together
• Honor force-draft so nothing publishes unreviewed
• Return the affected ID and link for chaining

Combining it with other abilities

Abilities are most powerful chained. On its own, nibwp/forms-manage does one thing well; in a workflow it becomes a step in something larger. A common pattern is to use a read ability such as nibwp/wp-search or nibwp/wp-list-posts to find the right targets, then act on them — the agent decides the sequence, and NIBWP keeps every individual call validated and logged. This is the difference between an agent that can talk about your site and one that can methodically work it.

Safety & control

NIBWP is built so that capable abilities stay controllable. For nibwp/forms-manage that means:

Best practices

• Stay in draft — keep force-draft on so writes land as drafts you approve.
• Find, then write — chain a read ability first so you act on the right targets.
• Batch with limits — rate limits stop a runaway loop; let the agent report progress.
• One token per client — scope and revoke independently per agent.

Specification

FAQ