Posteady

List published posts with metrics

list_posts

Read-only

List published Threads/X/LinkedIn/TikTok/Instagram/YouTube/Facebook posts with engagement metrics (views, reach, likes, replies, shares...). sort=top orders posts by performance, and each post includes its performance metrics. Each post's postId is the native platform post ID. repost_post works for accounts whose capabilities.repostPosts is true. TikTok requires a Business Developers connection; this tool reads synced video/photo posts with native IDs. Pending video jobs are reported by get_publish_status. TikTok includes shares, mediaType, and metricsUpdatedAt; unavailable or unsupported metrics are null. Instagram reads synced professional-account media with native IDs; unsupported repost and quote metrics are null. YouTube reads synced videos with native video IDs and includes title, mediaType (VIDEO or SHORTS), and metricsUpdatedAt; views, likes, and replies are available and other metrics are null. Facebook reads non-deleted synced Page posts with native IDs and mediaType; unavailable metrics and unsupported reach, quotes, and bookmarks are null. By default this searches across ALL your workspaces and labels each post with its workspace; pass workspaceId to narrow to one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_posts"
  }
}

Input Schema

Name	Required	Description
`sort`	No	recent = newest first (default). top = highest views first.
`limit`	No	Max posts to return (default 20).
`provider`	No	Filter by platform.
`accountId`	No	Filter by account (from list_accounts).
`workspaceId`	No	Narrow to a single workspace (ID from list_workspaces). Omit to search across ALL your workspaces (each post is labeled with its workspace).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's job is to add operational context, and it does: per-platform prerequisites (TikTok Business Developers connection), the null convention for unavailable/unsupported metrics, and per-provider field availability (shares, mediaType, metricsUpdatedAt). It never addresses pagination or rate/limit behavior, which is the main remaining gap.

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 front-loaded opener is strong, but the body is a long provider-by-provider inventory with visible redundancy: "each post includes its performance metrics" repeats the first sentence and "sort=top orders posts by performance" repeats the next. It is informative but not tight, and the workspace-default note is buried at the very end.

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?

There is no output schema, so the description carries the return-value burden, and it does explain key response fields: postId is the native platform ID, each post carries a workspace label, and TikTok/YouTube/Facebook add mediaType and metricsUpdatedAt. Pagination and total-count behavior remain unspecified, which keeps it from a 5.

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 the schema already documents sort, limit, provider, accountId and workspaceId in detail. The description only restates sort=top as "orders posts by performance," which is actually vaguer than the schema's "highest views first," and otherwise adds no parameter meaning. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List published ... posts with engagement metrics" gives a specific verb, resource and scope, and the word "published" implicitly separates it from list_scheduled_posts and list_media. The enumerated platforms and metric set tell an agent exactly what surface it covers without opening the schema.

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?

It routes the agent elsewhere in two concrete cases: pending video jobs go to get_publish_status, and reposting requires capabilities.repostPosts and repost_post. It also explains the default all-workspaces behavior versus passing workspaceId. It never states an explicit when-not-to-use vs list_scheduled_posts or list_media, so it stops short of a 5.

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

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

Resources

Need Help?