AutomateSocials

Edit a post

edit_post

Changes a post that already exists: its words, its pictures, the platforms it is for, or any combination. Pass only what changes; everything else stays. This is how you rewrite a draft or swap its image - do not write a second copy. Read it with get_post first when you are changing the words, since you cannot rewrite what you have not read. Works on drafts and on posts that are scheduled but have not gone out; a published post cannot be edited here.

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": {
      "postId": "<postId>"
    },
    "name": "edit_post"
  }
}

Input Schema

Name	Required	Description
`text`	No	New words. Leave out to keep what is there.
`title`	No	Internal title, never published.
`postId`	Yes	The post, by id or by the number shown to the user (#2).
`mediaIds`	No	Replaces the pictures or video. Pass an empty list to take the media off entirely.
`variants`	No	Per-platform changes, keyed by platform (facebook, instagram, x, linkedin, tiktok, youtube). Only the platforms and fields named change; the rest stays.
`platforms`	No	Which platforms it is for, if that is changing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare write/non-destructive/open-world, and the description adds genuine context beyond them: partial-update semantics ("Pass only what changes; everything else stays") and a lifecycle restriction limiting edits to drafts and not-yet-published scheduled posts. It stops short of covering permissions or what happens to an in-flight scheduled publish if edited, so it is strong but not exhaustive.

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?

Front-loads the core operation, then layers patch semantics, prerequisite, and lifecycle limits in four tight sentences with no filler. Each sentence carries a distinct rule an agent must apply.

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 nested, six-parameter mutation with no output schema, the description covers the operation, patch behavior, prerequisite read, and state limits — enough to call it correctly. It omits what the response contains (e.g. whether the updated post is returned) and failure behavior for invalid platforms, which are the remaining gaps.

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?

Schema coverage is 100%, so baseline is 3, but the description adds the key patch contract — omitted fields are preserved — which governs correct usage across all six parameters, including the nested variants. It does not go further into variant/platform value formats, so it sits just above baseline rather than at 5.

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 ("Changes a post that already exists") and enumerates the editable facets: words, pictures, target platforms, or any combination. It explicitly distinguishes itself from create_post ("do not write a second copy") and pairs with get_post, so an agent can place it among siblings without reading the schema.

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 concrete use cases (rewrite a draft, swap its image), a prerequisite ("Read it with get_post first when you are changing the words"), and an explicit exclusion ("a published post cannot be edited here"). The when-to-use, when-not, and alternative tool are all named.

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

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