Skip to main content
Glama
Sign In

Socialync

by io.github.JackVitick
OverviewDiscussionsAdmin

get_comments

Read-only

Read the comments on one of the user's published posts: who said what, when, and the replies under each. Works for Instagram, YouTube, Threads, LinkedIn Company Pages (paid plans) and Bluesky; X, TikTok and Facebook comments are managed in the Socialync app. Use it to see what the audience is asking or reacting to, to spot ideas for the next post, or to find a comment to answer with reply_to_comment. Get post ids from get_top_posts or get_post_history. Shows up to the 60 most recent comments.

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>"
    },
    "name": "get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post id (the "id" from get_top_posts or get_post_history).
profileIdNoThe Socialync profile the post belongs to. Usually not needed: the post's own profile is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior. The description adds useful context beyond that: platform coverage, the Socialync app fallback for unsupported platforms, and a 60-comment recent limit.

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?

The description is front-loaded with the core action and return shape, then use cases, id sourcing, and limits. It is somewhat dense with platform details, but each sentence contributes useful selection or invocation context.

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?

There is no output schema, so the description carries the burden of explaining returns; it does so by describing commenter, content, timing, replies, and recency limits. Combined with platform availability and id sourcing, it is complete enough for correct selection and invocation.

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 both parameters are already documented in the schema. The description reinforces the postId source but does not add meaning beyond the schema for profileId or parameter behavior.

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: read comments on a published post, including replies and timestamps. It distinguishes this from reply_to_comment by casting that sibling as the action to take after finding a comment.

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 use cases, names the sibling used for follow-up action, and tells the agent where to get post ids. It also clarifies which platforms are supported and which are handled elsewhere.

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