xpost

Project rules and settings

get_project

Read-onlyIdempotent

The project's settings, read before writing: timezone (the clock every bare time is on), queue (its posting schedule and next free slots — scheduled_at: "next_slot" takes one), approval (whether agent posts wait for a person), posts_today (this key's remaining daily allowance) and publishing (whether anything written here can go out at all — read it before writing, not after).

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`ok`	No	Present and false only on a refusal.
`name`	No
`error`	No	What was refused, in a sentence, when `ok` is false.
`queue`	No
`approval`	No
`timezone`	No	Every bare timestamp is read in this zone.
`retriable`	No	False when asking again cannot change the answer.
`signature`	No
`error_code`	No	Machine reason for a refusal.
`guardrails`	No
`publishing`	No
`posts_today`	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.

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"
+}

Changed1 schema field changedSep 28, 2026

addedOutput schema / properties / publishing / properties / plans_link

Added value: +{
+  "description": "The plans page as a ready-made Markdown link. Where `needs_plan` is true, include it as-is.",
+  "type": "string"
+}

First observedSep 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it describes how settings gate writes ('whether agent posts wait for a person', 'whether anything written here can go out at all') and clarifies the operational consequence of each field.

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 definition is front-loaded with the core purpose and then organizes details field-by-field with useful parentheticals. It is dense but not wasteful, though the single long sentence is slightly harder to scan than a more structured list would be.

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?

With no parameters, rich read-only annotations, and an output schema present, the description supplies everything an agent needs: what the settings mean, why they matter before writing, and how to interpret key values like queue.next_slot. Nothing essential is missing.

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 zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and it correctly focuses on the returned settings instead.

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 description clearly identifies the resource as 'the project's settings' and enumerates the specific fields returned: timezone, queue, approval, posts_today, and publishing. It is distinguishable by content from sibling tools, but does not explicitly contrast itself with closely related tools like get_posting_rules, so it falls just short of a 5.

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?

The description provides strong usage guidance with 'read before writing' and the emphatic 'read it before writing, not after', telling the agent exactly when this tool is needed. It lacks explicit exclusions or named alternatives, which prevents a 5.

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.