xpost

Top posts

get_top_posts

Read-onlyIdempotent

Best-performing deliveries ranked by a metric, with caption, platform, username, metrics and live URL — what worked for this audience, as a study aid rather than a template.

Input Schema

Name	Required	Description
`limit`	No	Max results (default 10)
`format`	No	Filter to one format (feed post / reel / story)
`metric`	No	Ranking metric (default engagement)
`platform`	No	Filter to one platform, e.g. instagram
`since_days`	No	Window in days (default 30)

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.
`metric`	No
`retriable`	No	False when asking again cannot change the answer.
`error_code`	No	Machine reason for a refusal.
`since_days`	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"
+}

First observedSep 25, 2026

TDQS

A3.5/5.0

Behavior3/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 safety is covered by structured data. The description adds useful behavioral context — that results are ranked by a chosen metric and include a live URL — but does not mention defaults (limit 10, 30-day window), pagination, or whose posts are in scope.

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?

A single front-loaded sentence that leads with the core operation and return payload. The trailing 'study aid rather than a template' clause is interpretive but short and arguably aids intent; only mildly ornamental.

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 return values needn't be spelled out, and the annotations plus full schema coverage handle safety and parameters. The only real gap is scope — it is unclear whether this ranks the caller's own accounts' posts or broader data ('this audience' is vague).

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 description coverage is 100%, so all five parameters (limit, format, metric, platform, since_days) are already documented including defaults and enums. The description only reiterates that a metric drives ranking, adding little beyond the schema; baseline 3 applies.

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 operation — ranking deliveries by a metric — and enumerates the returned fields (caption, platform, username, metrics, live URL). This distinguishes it from list_posts (unranked) and get_post_metrics (a single post), though it never names those siblings 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?

The phrase 'what worked for this audience, as a study aid rather than a template' implies an exploratory/analytical use case, giving some context on intent. But it offers no explicit when-to-use versus alternatives such as get_post_metrics, get_insights, or get_best_times, leaving routing to inference.

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.