Ravenpost

Publish a post now

publish_post

Destructive

Publish an existing post (e.g. a draft) once the user confirms it, without editing its content. It does NOT publish by itself: the post waits for the user, who confirms it with the Publish button on the post card or on Ravenpost (the result says where); until then nothing goes out and the post stays exactly as it was — a draft stays a draft, a post on the calendar keeps its time. Call it only on the user's explicit instruction, and once: a second call only asks them again. A post that has already been published, or is publishing right now, is refused rather than sent twice. Once confirmed it goes public on every target account at once, and that cannot be undone from here: delete_post removes only Ravenpost's copy, and a post on Instagram, TikTok, Threads and YouTube cannot be taken down through Ravenpost at all.

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": "publish_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post id to publish now

Output Schema

Name	Required	Description	Default
`ok`	No
`post`	No
`preview`	No
`awaitingConfirmation`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: the tool does not publish by itself, the post waits for user confirmation via the Publish button, duplicate/already-published posts are refused rather than double-sent, and confirmation pushes live to every target account irreversibly. This is consistent with destructiveHint=true, idempotentHint=false, and openWorldHint=true.

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 critical safety facts (explicit user instruction, once only, irreversible, delete_post only removes the Ravenpost copy) are front-loaded in a single dense paragraph. It is long, but nearly every clause carries operational meaning; slight tightening would help.

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

Completeness5/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 needn't be explained, and the description still notes 'the result says where' confirmation occurred. For a single-parameter, destructive, real-world publishing action, an agent has everything needed to call it correctly and caution appropriately.

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?

Only one parameter exists and schema description coverage is 100% ('The post id to publish now'), so the schema fully documents it. The description adds no format or sourcing detail for postId, which is acceptable at baseline.

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 ('Publish an existing post (e.g. a draft)') and carves out scope explicitly ('without editing its content'). An agent can distinguish this from create_post, update_post, or schedule_post without opening any schema.

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?

Gives clear invocation conditions: 'Call it only on the user's explicit instruction, and once: a second call only asks them again.' It explains the deferred-confirmation behavior. It does not, however, reference the sibling confirm_publish or clarify the relationship with preview_post/schedule_post, leaving some routing ambiguity.

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

All Ravenpost 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.