uplika

List replies to a post

list_replies

Read-only

The whole reply thread under a post, nested replies included. truncated tells you we stopped before the end. The count here can differ from the replies metric in get_insights, which is normal. If the response carries bridge, bridge.nextStep says what is needed: run_wake means Chrome with the extension is closed, so tell the person bridge.userMessage with the bridge.wake command for their OS and retry once after they say Chrome is open; ask_user_login / ask_user_update mean tell the person bridge.userMessage. Do not retry more than twice.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	A publish id (post_…), the post's own id on the channel, or a post link (the URL you would open in a browser to see it). Links work for posts written in the channel's own app too, as long as the account is connected here.
`workspaceId`	No	Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Which workspace this is for. Only needed when the account has more than one — the error tells you the ids when it matters. Leave it out if it is already decided; do not ask the person again.",
+  "type": "string"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / id / description

Previous value: -"A publish id (post_…), a channel-side id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the channel's own app too, as long as the account is connected here."New value: +"A publish id (post_…), the post's own id on the channel, or a post link (the URL you would open in a browser to see it). Links work for posts written in the channel's own app too, as long as the account is connected here."

Changed1 schema field changedAug 12, 2026

changedInput schema / properties / id / description

Previous value: -"A publish id (post_…), a Threads media id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the Threads app too, as long as the account is connected here."New value: +"A publish id (post_…), a channel-side id, or a post link (https://www.threads.com/@handle/post/CODE). Links work for posts written in the channel's own app too, as long as the account is connected here."

First observedAug 10, 2026

TDQS

A4/5.0

Behavior5/5

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

Well beyond the readOnly/openWorld/non-destructive annotations, it discloses that results may be truncated via a `truncated` flag, that the count can legitimately differ from get_insights, and it decodes the `bridge` error payload into concrete nextStep actions (run_wake, ask_user_login, ask_user_update) with a two-retry cap. This is unusually rich failure-mode disclosure.

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?

Purpose is front-loaded in the first sentence, followed by caveats and then the bridge handling in ascending order of operational rarity. The bridge paragraph is dense, but every clause maps to a distinct action an agent must take.

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 output schema, the description steps in and explains the two non-obvious response aspects an agent will encounter: `truncated` and the `bridge` object. Combined with complete schema coverage and safety annotations, nothing needed to call this correctly is missing.

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 both `id` (publish id, channel id, or post link) and `workspaceId` (only needed for multi-account, error reports ids) are already fully documented in the schema. The description adds no parameter meaning, which is fine but earns only the baseline.

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 first sentence names the resource and its scope precisely: the whole reply thread under a post, nested replies included. It distinguishes itself from the replies metric in get_insights, though it does not route to a true selection alternative among siblings like list_mentions or read_conversation.

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?

Usage is implied by the resource (fetch replies to a given post) and the description gives operational guidance for failures, but it never states when to prefer this tool over siblings or any precondition beyond the id. The guidance offered is retry behavior rather than tool-selection guidance.

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

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