Skip to main content
Glama

uplika

by com.uplika
OverviewDiscussionsAdmin

Reply to a post

reply
Destructive

Reply to a post or to a reply. Leave replyTo empty to reply to the post itself; pass a reply id from list_replies to nest a reply under that reply. Like publish, this returns before the reply is live unless you pass wait: true, which holds the response until it is out (up to 10 seconds). Otherwise call get_post with the returned id to see the final status and link. 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
NameRequiredDescriptionDefault
idYesA 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.
waitNoHold the response until the reply is really out, up to 10 seconds, so you can say it is live. If it is still going you get the usual publishing response; poll get_post. Defaults to false.
secretNoNaver Blog only: post it as a secret comment that only the blog owner can read. Other channels refuse it.
contentYes
replyToNoReply id from list_replies. Omit to reply to the post itself.
workspaceIdNoWhich 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.

  1. Changed1 schema field changed
    • addedInput schema / properties / wait
      Added value: +{
+  "description": "Hold the response until the reply is really out, up to 10 seconds, so you can say it is live. If it is still going you get the usual publishing response; poll get_post. Defaults to false.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / secret
      Added value: +{
+  "description": "Naver Blog only: post it as a secret comment that only the blog owner can read. Other channels refuse it.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed1 schema field changed
    • 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."
  5. Changed1 schema field changed
    • 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."
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, destructive, open-world write; the description goes well beyond that by disclosing asynchronous completion ('returns before the reply is live'), the 10-second wait ceiling, and a full bridge-error playbook (run_wake, ask_user_login, ask_user_update) with what to tell the person. Nothing here contradicts the destructiveHint annotation, since it publishes content.

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-loaded: the core reply semantics and replyTo behavior come first, then async behavior, then the bridge error ladder. It is long, but each clause carries operational weight; only the bridge detail could be trimmed without losing meaning.

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-value burden and does so: it explains the returned id, the bridge/bridge.nextStep field, and how to check final status via get_post. For a 6-parameter publishing tool with error-recovery needs, nothing essential 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 coverage is 83%, so the schema already documents id, wait, replyTo, secret and workspaceId; the description's parameter content (empty replyTo, wait:true) largely restates the schema rather than adding syntax or format detail. Baseline 3 is appropriate when the schema does the heavy lifting.

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 first sentence states a specific verb+resource ('Reply to a post or to a reply') and immediately distinguishes the two modes via the replyTo parameter. It names and routes to siblings (list_replies, get_post, publish), so an agent can tell it apart from publish or send_dm without opening anything else.

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?

Explicit when-to-use for every branch: omit replyTo to reply to the post, pass a list_replies id to nest, pass wait:true to block, otherwise poll get_post with the returned id. It also gives a bounded retry policy ('Do not retry more than twice'), which is rare and genuinely actionable.

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

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