xpost

List connected accounts

list_accounts

Read-onlyIdempotent

The connected accounts and what each will publish. ref ("x:someone") is what create_post accounts takes. limits carries caption_chars_available (room for your words), max_media, media_required and video_seconds; can carries placements, first comment, people tags, documents and mixed media. These describe the connection, not the platform's brochure. posts_left_today (where present) is how many more posts that account can publish before resets_at (midnight UTC) — schedule past it, not into a full day, which is refused. connect_url is the page where an account is connected — hand it over whenever a platform they asked for is missing. An empty list adds connect_message; a project that has never published adds never_posted_message, which says what to offer them next.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	No	Present and false only on a refusal.
`data`	No
`error`	No	What was refused, in a sentence, when `ok` is false.
`retriable`	No	False when asking again cannot change the answer.
`error_code`	No	Machine reason for a refusal.
`connect_url`	No
`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.
`connect_message`	No
`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."

Changed2 schema fields changedOct 14, 2026

changedOutput schema / properties / data / items / properties / limits / properties / caption_chars_available / description

Previous value: -"Caption room left once the project's signature is added."New value: +"Caption room left for your words."

addedOutput schema / properties / data / items / properties / posts_left_today

Added value: +{
+  "additionalProperties": {},
+  "description": "Absent where the account has no such daily allowance.",
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "remaining": {
+      "type": "number"
+    },
+    "resets_at": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

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

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses real behavioral detail: empty results append `connect_message`, brand-new projects append `never_posted_message`, and scheduling into a full day is refused with a UTC-midnight reset. It notably warns that limits reflect the actual connection, not the platform's advertised capability. It doesn't describe ordering or pagination, but with zero parameters the payload is presumably a single list.

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?

Purpose is front-loaded, but the bulk is an enumerated tour of return fields (`limits`, `can`, `posts_left_today`, `connect_url`) that an output schema already covers. The 'not the platform's brochure' clarification earns its place; the field inventory is partially redundant.

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 zero parameters, closed-world read-only annotations and an output schema, the definition needs only to route the agent and flag behavioral edge cases. It does both, including the missing-platform handoff and never-posted case. Nothing required for correct invocation is absent.

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?

The tool takes no parameters, which is the documented baseline for full marks. The description spends its space on return-field semantics instead, which is not what this dimension measures but also not harmful.

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?

The opening fragment 'The connected accounts and what each will publish' identifies the resource and scope, and the title supplies the verb. It also differentiates itself by naming create_post's `accounts` parameter as the downstream consumer, which no sibling does. It stops short of an explicit 'list/read' verb and doesn't contrast with list_connection_issues.

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?

Provides concrete usage conditions: use `ref` to fill create_post's `accounts`, hand over `connect_url` when a requested platform is missing, and schedule around `posts_left_today` rather than into a refused full day. These are operating instructions rather than explicit when-to-call-this-vs-alternative guidance, so no exclusion clause is given.

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.