Skip to main content
Glama
Upload-Post

Upload-Post

Official

Act on a published post

post_action
Idempotent

Manage published Bluesky and Telegram posts by bookmarking, pinning, adjusting reply or quote settings, reacting, or removing reactions, with a preview step for user approval before changes.

Instructions

Actions on a published post. Bluesky: bookmark / unbookmark (private), pin / unpin on the profile (unpin takes no post_id), reply_settings (who can reply: reply_settings everyone, nobody, mention, following, followers or list:, one or several), quote_settings (quote_settings disable_quotes or everyone), detach_quote / reattach_quote (quote_uri = the post that quotes this one). Telegram: react (emoji, or params.telegram_reaction, params.telegram_is_big), delete_reaction (removes another person's reaction in a group: params.user_id or params.actor_chat_id, needs confirm). Bluesky likes and reposts are not available. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user": "<user>",
      "platform": "<platform>",
      "action": "<action>"
    },
    "name": "post_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name.
emojiNoTelegram react only: one emoji.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. Telegram reaction extras. Leave out what you do not want to change.
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.
post_idNoBluesky: at:// URI or bsky.app link. Telegram: the post id returned by the upload.
platformYes
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
quote_uriNoBluesky detach_quote / reattach_quote only.
quote_settingsNoBluesky quote_settings action only.
reply_settingsNoBluesky reply_settings action only.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that bookmarks are private, that unpin takes no post_id, that delete_reaction removes another person's reaction and needs `confirm`, and that nothing is sent until `confirmed: true`. The preview-then-confirm gate is exactly the kind of behavioral context annotations cannot convey. Minor tension: irreversible deletions are described while destructiveHint=false, but the confirm gate plausibly justifies that annotation.

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?

Dense and front-loaded, with platform-grouped action lists and the approval rule placed last where it is most actionable. The single long sentence enumerating Bluesky actions is heavy but every clause carries distinct operational information, so little could be cut without losing guidance.

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?

For an 11-parameter, multi-action, nested-params tool this covers the essentials: action applicability, platform split, confirmation protocol, and exclusions. Return values need not be described since an output schema exists. A short note on what the preview response contains would close the last gap.

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?

Schema coverage is already 82%, so the baseline is 3, and the description adds real meaning on top: which parameters apply to which action (quote_uri only for detach/reattach_quote, emoji only for Telegram react, params.telegram_reaction/telegram_is_big, params.user_id or actor_chat_id for delete_reaction). It also clarifies the accepted reply_settings values including the list:<at-uri> form.

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 opening line is generic ('Actions on a published post'), but the body enumerates the exact operations per platform (bookmark/unbookmark, pin/unpin, reply_settings, quote_settings, detach/reattach_quote, react, delete_reaction), so an agent can tell precisely what the tool does. It also explicitly excludes Bluesky likes and reposts, which sharpens the boundary against siblings like repost_post.

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?

Usage is spelled out per platform and per action, including the notable exclusion that Bluesky likes/reposts are not available here, which implicitly routes the agent elsewhere. The approval workflow (call without `confirmed` for a preview, then repeat with `confirmed: true`) is stated as a required procedure. It stops short of naming sibling tools explicitly for the excluded operations.

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

Deploy Server

Other Tools