Postemi: Social Media Scheduler

update_post

Change a scheduled, draft or failed Postemi post from the Postemi app: its text, thread parts or comments, media, settings and time. A published post cannot be changed.

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>",
      "date": "<date>",
      "type": "<type>",
      "postsAndComments": "<postsAndComments>"
    },
    "name": "update_post"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	ISO 8601 UTC publish time.
`type`	Yes
`postId`	Yes	The postId to change, from list_posts.
`settings`	No
`postsAndComments`	Yes

Output Schema

Name	Required	Description	Default
`errors`	No
`output`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description's real addition is the state restriction on which posts are mutable, which is valuable and not in the annotations. It does not disclose that four parameters are mandatory (implying a full-content replacement rather than a patch) or what happens to unset settings/attachments.

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?

Two sentences, zero filler, with the mutability scope front-loaded before the prohibition. Every clause carries information an agent needs.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and the state rule is covered. What is missing for a five-parameter mutation tool with 40% schema coverage is guidance on the required-field/full-replacement nature of the call and on how `type` interacts with the edit.

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 only 40%, so the description has to compensate and it partially does: media/settings/text/time map onto postsAndComments, settings and date. But the `type` enum (schedule/draft/now) is entirely unaddressed and the relationship between editing content and choosing a new publish state is undefined.

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?

Specific verb (Change) plus resource (Postemi post) plus the exact facets affected (text, thread parts/comments, media, settings, time). The closing sentence carves out published posts, which distinguishes it cleanly from create_post, delete_post and get_post.

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

Usage Guidelines4/5

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

It states the eligibility condition precisely — only scheduled, draft or failed posts may be edited, and published ones cannot — which is the main decision an agent needs. It does not explicitly route to siblings such as get_post for reading or preview_post for verification, so it stops short of full alternative guidance.

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

All Postemi: Social Media Scheduler 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.