Ravenpost

Get a post

get_post

Read-onlyIdempotent

Get one post by id, including its media, per-account targets and publish status — and, when a publish asked for through an assistant is waiting for the user to confirm it, what it would do and where they can confirm it (publishRequest). Clients that render MCP Apps also show it as it looks on each destination platform, with the Publish button for a waiting publish.

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

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post id

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely valuable behavioral context beyond that: a conditional field (publishRequest) that appears only while an assistant-initiated publish awaits user confirmation, plus how MCP Apps clients render platform previews. It does not say what happens for a nonexistent or unauthorized post id.

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?

The core purpose is front-loaded in the first clause, which is good. But the sentence sprawls through nested em dashes and a parenthetical, and the trailing MCP Apps rendering sentence is client-UI detail of marginal use to an agent selecting or invoking the tool.

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?

With an output schema present, return-value documentation is not needed, and the description still flags the one non-obvious conditional output (publishRequest). For a single-param read tool this is close to complete; only error/not-found behavior is unaddressed.

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, postId, and schema description coverage is 100%, so the schema already carries the semantics. The description adds nothing about the id's format or origin (e.g. where to obtain it), which leaves this at the baseline.

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?

States a specific verb and resource (get one post by id) and enumerates what comes back: media, per-account targets, publish status. It implicitly distinguishes itself from list_posts by emphasizing a single post by id, but never names a sibling alternative explicitly.

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?

Usage is only implied — an agent can infer this is the retrieval call for a known post id, and the mention of publishRequest hints at the pending-confirmation scenario. There is no explicit when-to-use/when-not guidance pointing at preview_post, list_posts, or get_analytics.

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.