posterly

list_comments

Read-onlyIdempotent

Social inbox comments and replies for Instagram, Facebook Pages, Threads, and LinkedIn Pages (Pro plan or higher plus posts:read). Without comment_id: list comments filtered by account, platform, unread/flagged, search, or since/until dates, with limit/offset paging. With comment_id: one comment and its replies; only workspace_id may be added. YouTube and TikTok are refused rather than returned as an empty list. They stay off until each platform is reviewed and an inbox provider exists.

Input Schema

Name	Required	Description
`limit`	No	Rows to return. Default 50.
`since`	No	ISO date/time, inclusive.
`until`	No	ISO date/time, inclusive.
`filter`	No	Default all.
`offset`	No	Rows to skip.
`search`	No	Search comment content or author username.
`platform`	No
`account_id`	No	From list_accounts.
`comment_id`	No	One comment and its replies.
`workspace_id`	No	Omit to search all your workspaces, or pass an ID from whoami.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 21, 2026

changedInput schema / properties / account_id / description

Previous value: -"Social account ID from list_accounts."New value: +"From list_accounts."

changedInput schema / properties / comment_id / description

Previous value: -"One comment (from a list call) with its replies."New value: +"One comment and its replies."

changedInput schema / properties / filter / description

Previous value: -"Comment filter. Defaults to all."New value: +"Default all."

changedInput schema / properties / limit / description

Previous value: -"Number of comments to return. Default 50, max 100."New value: +"Rows to return. Default 50."

changedInput schema / properties / offset / description

Previous value: -"Skip this many comments before returning results."New value: +"Rows to skip."

removedInput schema / properties / platform / description

Removed value: -"instagram, facebook, threads, or linkedin."

addedInput schema / properties / since

Added value: +{
+  "description": "ISO date/time, inclusive.",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "ISO date/time, inclusive.",
+  "type": "string"
+}

changedInput schema / properties / workspace_id / description

Previous value: -"Optional. Omit to search every workspace you belong to; pass a workspace ID from whoami to limit to one."New value: +"Omit to search all your workspaces, or pass an ID from whoami."

First observedOct 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds crucial behavioral constraints far beyond the schema and annotations. It details specific operational requirements, such as needing 'Pro plan or higher' and the 'posts:read' permission. It also manages user expectations by stating the current lack of support for certain platforms and its future development status.

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 description is highly dense, trying to cover platform scope, operational modes, and support limitations all in one paragraph. While the information is vital, it is not optimally structured or concise, leading to slight clutter.

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?

The tool definition is extremely comprehensive. It provides all necessary context for an agent to determine platform compatibility, necessary permissions, functional mode (search vs. fetch), and hard limitations (unsupported platforms), making it contextually complete for its complexity.

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?

Although schema coverage is high (90%), the description provides valuable context that the schema lacks. It clarifies that the tool's functionality changes drastically depending on whether comment_id is used, and it clarifies the scoping of workspace_id (i.e., omitting it searches all workspaces).

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?

The description clearly defines the tool's purpose as listing 'Social inbox comments and replies' across specific platforms like Instagram, Facebook, Threads, and LinkedIn. It also distinguishes between two core behaviors: bulk filtering without a comment_id, and retrieving a specific comment and its replies when comment_id is provided.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit usage guidelines by defining the operational modes based on the presence of the comment_id parameter. Furthermore, it provides strong negative usage constraints, specifically stating that YouTube and TikTok are refused by this tool rather than returning an empty list, helping the agent decide when the tool is inapplicable.

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

All posterly 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?