Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

reply_to_comment

Destructive

Reply to one comment on one of the user's published posts, as the user's own account, on Instagram, Threads, LinkedIn Company Pages (paid plans) or Bluesky. The reply is public and goes out immediately. Before calling, show the user the comment and the exact reply and get their explicit confirmation in chat, one reply at a time; never reply in bulk or without the user seeing each one. If the user has switched on the publish confirmation dialog in Socialync settings and their client supports MCP elicitation, Socialync also shows a dialog; a decline sends nothing and comes back as success false with consent "declined". YouTube and X replies are sent by the user in the Socialync app. Get the commentId from get_comments. Limit: 30 replies per day.

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": {
      "postId": "<postId>",
      "commentId": "<commentId>",
      "text": "<text>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe reply text. Limits: Instagram 2,200, LinkedIn 1,250, Threads 500, Bluesky 300 characters.
postIdYesThe post the comment is on (the "id" from get_top_posts or get_post_history).
commentIdYesThe comment to reply to, exactly as get_comments returned it.
profileIdNoThe Socialync profile the post belongs to. Usually not needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the reply is public and immediate, that confirmation is required in chat, and how the optional Socialync dialog behaves when declined. It also states the 30-replies-per-day limit and which platforms are out of scope for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded and every sentence carries operational value: scope, immediacy, confirmation requirements, platform exclusions, commentId source, and rate limit. There is no filler or repetition beyond safety reinforcement.

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?

For a public, destructive mutation tool with no output schema, the definition covers the critical operational details: confirmation, immediacy, platform availability, rate limit, and required identifiers. Nothing essential for correct invocation appears 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 parameter meanings are already carried by the schema. The description adds only that commentId comes from get_comments, which is minor additional context rather than meaningful expansion of parameter semantics.

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 description states a specific verb and resource: replying to one comment on one of the user's published posts, as the user's own account. It names supported platforms and explicitly notes that YouTube and X replies happen in the Socialync app, which helps distinguish the tool's scope from sibling workflows.

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?

It gives explicit before-calling guidance: show the user the comment and exact reply, obtain explicit confirmation, and handle one reply at a time. It also says never to reply in bulk and points to get_comments for the required commentId.

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

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