Skip to main content
Glama

posterly

by ly.poster
OverviewDiscussionsAdmin

manage_comment

Destructive

Act on an inbox comment (Pro plan or higher plus posts:write). action=reply (comment_id, content): reply to an Instagram, Facebook Page, Threads, or LinkedIn Page comment; type private is Instagram only, the others are public replies only. action=update (comment_id, is_hidden and/or is_read): hide or unhide it on the platform, or mark it read or unread; reversible, no confirm needed. action=delete (comment_id): delete an Instagram or Facebook Page comment, irreversible and admin only; Threads replies cannot be deleted, hide them instead. reply and delete use preview then confirm: call without confirm to get a preview and preview_id, show it, then call again with confirm=true and that preview_id.

Input Schema

NameRequiredDescriptionDefault
typeNoreply: public (default) or private. Private is Instagram only.
actionYesreply, update, or delete.
confirmNoreply and delete: Leave out to get a preview. Set true only after the user explicitly approved it, with the preview_id.
contentNoreply: reply text to post.
is_readNoupdate: mark the comment read or unread in posterly.
is_hiddenNoupdate: hide or unhide the comment on Instagram, Facebook, or Threads.
comment_idYesComment ID from list_comments.
preview_idNoThe preview_id from the preview call. Required with confirm: true for actions that preview first.
workspace_idNoOmit to search all your workspaces, or pass an ID from whoami.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"reply and delete: Leave out to get a preview and preview_id. Set true only after the user explicitly approved the preview, together with preview_id."New value: +"reply and delete: Leave out to get a preview. Set true only after the user explicitly approved it, with the preview_id."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations (destructiveHint=true, idempotentHint=false): it distinguishes which actions are reversible ('update ... reversible, no confirm needed') from the irreversible one, flags delete as admin-only, and describes the preview_id handshake that gates reply and delete. This is exactly the behavioral context an agent needs for a mutating tool.

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?

One dense paragraph, but it is front-loaded with the auth requirement and purpose before the three actions, and every clause carries meaning (platform limits, reversibility, preview flow). It reads as a run-on sentence, which costs it a point.

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 a 9-parameter, three-action tool with no output schema, the description covers permissions, platform exclusions, reversibility, and the preview/confirm return value (preview_id). It does not describe the success response for update or reply, leaving a minor 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 description coverage is already 100%, so the baseline is 3, but the description adds real value by grouping parameters by action (which fields apply to reply vs update vs delete) and by treating type=private as Instagram-only. It stops short of adding syntax or format detail beyond what the schema states.

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?

Opens with a specific verb+resource ('Act on an inbox comment') and then enumerates the three actions with their platform scope. It clearly distinguishes itself from the sibling list_comments, which is the read counterpart referenced by comment_id.

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?

States per-action when-to-use, plan/permission prerequisites (Pro plan or higher plus posts:write, admin only for delete), and an explicit alternative when an action is unavailable ('Threads replies cannot be deleted, hide them instead'). It also requires the preview-then-confirm sequence before irreversible operations.

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

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