OrgLines

SEO: Undo applied proposal

seo_undo_apply

Destructive

Undo an applied proposal exactly: the page's or post's previous title and meta come back, a draft created by the apply is deleted (only while nobody has edited it). Refused when someone changed that title/meta since — force=true overwrites their change; ask the person first. apply_id comes from seo_apply_proposal or seo_get_cluster's active_apply. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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": {
      "apply_id": "<apply_id>"
    },
    "name": "seo_undo_apply"
  }
}

Input Schema

Name	Required	Description	Default
`force`	No
`apply_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond destructiveHint=true, the description explains exactly what is restored, what draft is deleted and under what condition, why the operation may be refused, and the effect of force=true. It also discloses the proposed-only confirmation flow with status, action_id, and plan_token.

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 action and effects, then conditions, parameter sourcing, and confirmation flow. Every sentence adds operational value without repetition.

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, confirmation-gated tool with no output schema, the definition covers effects, refusal conditions, force behavior, parameter sourcing, and the confirmation response shape. Nothing essential for correct invocation is missing.

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?

With 0% schema description coverage, the description compensates by explaining that apply_id comes from seo_apply_proposal or seo_get_cluster's active_apply and that force=true overwrites another person's change. It does not restate type constraints, but those are in 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?

The description states a specific verb and resource: undo an applied proposal, with precise effects on title, meta, and draft deletion. It also distinguishes the operation from apply and confirmation flows by naming apply_id sources and the confirmation protocol.

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

Usage Guidelines5/5

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

It explicitly says when the undo is refused, when force=true is appropriate, and that the person should be asked first. It also routes the agent to seo_apply_proposal or seo_get_cluster for apply_id and to confirm_action for completion.

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

All OrgLines tools Inspect

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

Need Help?