xpost

List posts

list_posts

Read-onlyIdempotent

Recent posts with status, publishes, mediaIds and, on a rejected post, rejectionReason — the person's own words on what to change with update_post (often empty after a one-tap rejection). Filter with status (one or several), limit, and from/to on the scheduled time. A post still waiting carries approval_link. filter echoes what applied. An empty list with nothing filtered adds never_posted_message, which says what to offer them next.

Input Schema

Name	Required	Description
`to`	No	Only posts whose scheduled time is at or before this instant.
`from`	No	Only posts whose scheduled time is at or after this instant (ISO 8601, Z or offset). With `from` or `to` the list runs soonest first and leaves out posts that have no time yet.
`limit`	No	How many, newest first (default 50, max 100)
`status`	No	Only posts in this state (or any of these). Omit for all of them.

Output Schema

Name	Required	Description
`ok`	No	Present and false only on a refusal.
`data`	No	Newest first, camelCase here unlike the rest of this server. Up to `limit` (50 by default).
`error`	No	What was refused, in a sentence, when `ok` is false.
`filter`	No	What actually applied — null status means nothing was filtered.
`retriable`	No	False when asking again cannot change the answer.
`error_code`	No	Machine reason for a refusal.
`replaced_by`	No	The id the post has now, when you asked with one an edit retired. An edit gives a post a new id: get_delivery_receipt and get_post_metrics answer for this current version (and `asked_for` is the id you sent); update_post and delete_post refuse with error_code `replaced`. Use this id from here on.
`never_posted_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / properties / replaced_by / description

Previous value: -"With error_code `replaced`: the id the post has now. An edit gives a post a new id; use this one."New value: +"The id the post has now, when you asked with one an edit retired. An edit gives a post a new id: get_delivery_receipt and get_post_metrics answer for this current version (and `asked_for` is the id you sent); update_post and delete_post refuse with error_code `replaced`. Use this id from here on."

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / replaced_by

Added value: +{
+  "description": "With error_code `replaced`: the id the post has now. An edit gives a post a new id; use this one.",
+  "type": "string"
+}

First observedSep 25, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that from/to flips ordering to soonest-first and drops untimed posts, that limit is newest-first, that `filter` echoes applied filters, that an unfiltered empty result adds never_posted_message, and that rejectionReason is often empty after a one-tap rejection. These are non-obvious response behaviors an agent could not infer.

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?

Dense single paragraph, front-loaded with the returned shape before filters and edge cases. Backtick-heavy phrasing makes it slightly hard to scan but every clause carries real information; no filler sentences.

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?

An output schema exists, so explaining individual return fields is partly redundant, but the conditional fields (approval_link, never_posted_message, filter echo) and the empty-result semantics are exactly the kind of conditional behavior a schema alone wouldn't surface. Nothing essential for correct invocation is missing.

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 100% and the schema already documents status-as-single-or-array, the from/to ordering side effect, and limit defaults. The description largely restates those same semantics rather than adding new meaning, so it sits at the baseline for high coverage.

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?

Concrete: lists recent posts, names the exact fields returned (status, publishes, mediaIds, rejectionReason) and the filters available. It's clearly a post-listing read, distinct from get_top_posts or get_post_metrics by virtue of being unfiltered-by-performance, though no sibling is named 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 implied through the data: a rejected post's rejectionReason is what to change 'with update_post', and never_posted_message 'says what to offer them next' — so the agent gets workflow cues. But there is no explicit statement of when to choose this over get_top_posts or get_insights.

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

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