SuperPost

Preview idea edit

preview_idea_edit

Read-onlyIdempotent

Previews a bounded idea edit without applying it. Supported edits include replace_idea_assistant_brief, which stores writing guidance for a future post separately from the thesis, conclusion, and post body.

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": {
      "ideaId": "<ideaId>",
      "expectedRevision": "<expectedRevision>",
      "operations": "<operations>"
    },
    "name": "preview_idea_edit"
  }
}

Input Schema

Name	Required	Description	Default
`ideaId`	Yes
`operations`	Yes
`idempotencyKey`	No
`expectedRevision`	Yes
`expectedRevisions`	No

Output Schema

Name	Required	Description	Default
`context`	Yes
`proposed`	Yes
`operations`	Yes
`reviewOnly`	Yes
`affectedIdeas`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds that the assistant brief is stored separately from the thesis, conclusion, and post body, which is useful behavioral context, but it does not describe validation, revision-conflict handling, or what the preview returns.

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

Conciseness4/5

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

The description is two sentences and front-loads the core action before adding a detail about one supported edit. It is not bloated, though the second sentence is selectively narrow for such a broad operations schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with five top-level parameters, deeply nested operation variants, and many sibling preview tools. The description only covers the preview intent and one operation kind, leaving an agent without enough guidance to construct most valid operations or understand revision/idempotency semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description explains only one of the many operation kinds, replace_idea_assistant_brief. It says nothing about ideaId, expectedRevision, expectedRevisions, idempotencyKey, or the other operation shapes such as replace_idea_thesis, set_idea_state, merge_ideas, and create_posts_from_idea.

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 description states a specific verb and resource: it previews a bounded idea edit without applying it. That clearly separates it from a mutation tool, though it does not name a sibling preview tool or explain how it differs from previewing content bundles or schedules.

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

Usage Guidelines2/5

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

The phrase 'without applying it' implies a dry-run use case, but the description gives no explicit guidance on when to call this preview versus another preview tool or the eventual apply operation. No exclusions or prerequisites are stated.

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

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