uplika

Open a post with replies and metrics

open_post

Read-only

Everything about one post in a single call: the text, the whole reply thread, and its metrics. This is the right tool when someone hands you a post link. Replies or metrics can come back null if the platform refused just that part. 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.4/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open world), yet the description adds real behavioral context: replies or metrics may come back null when the platform refuses that part, and the `bridge` object signals a Chrome/extension or auth problem with a defined remediation path. This is exactly the runtime nuance an agent cannot get from the schema.

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?

Front-loads the scope sentence before the failure handling, and there is no filler. The bridge/retry passage is long and reads more like error-recovery procedure than tool description, but every clause is actionable and the retry cap is stated tightly.

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 carries the return-shape burden and does so: it enumerates the three payload sections, flags nullable fields, and explains the `bridge` object's meaning. Nothing needed to call or interpret the response 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 `id` and `workspaceId` are already fully documented in the schema, including accepted id formats and the 'do not ask again' guidance. The description adds no syntax or format detail beyond what the schema provides, so the 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 resource and the exact payload it returns ('the text, the whole reply thread, and its metrics') plus a concrete trigger ('when someone hands you a post link'). This implicitly contrasts with narrower siblings like get_post and list_replies, but neither is named, so the differentiation is inferential rather than explicit.

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?

Gives an explicit selection condition ('the right tool when someone hands you a post link') and then prescribes behavior for edge cases: interpret `bridge.nextStep`, branch on `run_wake` vs `ask_user_login`/`ask_user_update`, surface `bridge.userMessage`, and never retry more than twice. That is far beyond what most definitions offer.

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?