PixelGlass

Replace a post's body

replace_post

Idempotent

On one site of the account, named in site. The whole body from Markdown, in the same forms create_post takes; blocks keep their rows when their fences keep their uuid comment. Send the version that get_post (or your last write) answered: a post saved since then refuses the write. The write is a revision the writer can undo. To add a picture, put it into the library with upload_media first, then paste the Markdown it answers.

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": "<site>",
      "post_id": "<post_id>",
      "markdown": "<markdown>",
      "version": "<version>"
    },
    "name": "replace_post"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	The site to work on, as list_sites names it
`post_id`	Yes
`version`	Yes	The post's version from get_post or your last write
`markdown`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Beyond annotations, it discloses optimistic concurrency (a stale version refuses the write), undoable revision semantics, block row preservation via UUID fence comments, and the upload_media workflow for images. These are substantial behavioral details that materially affect how an agent should invoke the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence carries operational information, but the opening is a sentence fragment and the dense, clause-heavy prose is not front-loaded around the action. It is concise but harder to parse than necessary.

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 four-required-parameter write with no output schema, it covers the critical version conflict, full-body replacement, undo behavior, block semantics, and media prerequisite. It still leaves post_id semantics and the exact post-write return/version behavior implicit.

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 50%; site and version are already described in the schema. The description adds meaning for markdown ('whole body', same forms as create_post) and reinforces version semantics, but post_id is never explained and site merely repeats 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 name/title and 'The whole body from Markdown' make clear this replaces a post body on a named site, and the version requirement distinguishes it from creation. However, the prose is elliptical and never explicitly distinguishes replace_post from sibling edit_post or update_block, so it is strong but not fully self-contained.

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

Usage Guidelines3/5

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

It supplies key operational preconditions: send the version returned by get_post or the last write, and upload media before pasting Markdown. It does not state when to choose this over edit_post/update_block or when not to use it, so usage is implied rather than fully guided.

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

All PixelGlass 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?