Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_save_post_preview

Saves proposed content as a native autosave for a published post or page without changing the published content. Open the returned preview_url while signed in as the same user. Existing differing autosaves are preserved and cause an error. After approval use wp_update_post to publish; preview URLs are temporary.

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": {
      "site_id": "<site_id>",
      "id": "<id>",
      "content": "<content>"
    },
    "name": "wp_save_post_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPublished post or page ID.
contentYesComplete proposed HTML or block markup.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read, non-destructive, non-idempotent mutation, and the description adds real substance beyond that: published content is untouched, conflicting autosaves are preserved rather than overwritten and produce an error, preview URLs are temporary, and a matching signed-in user is required. It stops short of saying whether a repeat save by the same user replaces its own prior autosave, which matters given idempotentHint=false.

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 short sentences, each carrying distinct operational information, with the core behavior and its scope stated first and the follow-up (wp_update_post) and caveats after. No filler.

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?

With no output schema, the description usefully names the returned preview_url and its temporary nature, and covers the main failure mode. It does not describe the error shape or what the autosave response contains beyond the URL, a minor gap for a mutation tool.

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 100%, so id/content/site_id are already fully documented and the description adds no per-parameter meaning. It does surface the otherwise undocumented return value preview_url, but that is output rather than input semantics, so the baseline 3 applies.

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 ("Saves proposed content as a native autosave for a published post or page") plus the crucial scope qualifier "without changing the published content", which separates it from wp_update_post and the other write siblings.

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?

Gives explicit workflow routing: use this for preview, then "After approval use wp_update_post to publish." It also states the precondition for viewing (the returned preview_url must be opened while signed in as the same user) and the failure condition (existing differing autosaves cause an error).

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

All Frontman for WordPress 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