comments

Ayrshare MCP — Comments

The engagement tools: read comments on a post, add a new top-level comment, and reply to an existing comment.

• API base (REST endpoints the tools wrap): https://api.ayrshare.com/api
• Comments are scoped to a post you already published; you need that post's id (returned by mcp__ayrshare__create_post — see ../post/SKILL.md).
• Profile scoping: profileKey argument or Profile-Key header. Pass a comment tool's profileKey argument to act as a specific client profile for that call, or set the connection's Profile-Key header to default the whole connection to it (the argument wins when both are set); with neither, calls act under the account's primary/Business profile. See ../getting-started/SKILL.md.

Supported platforms

The three comment tools accept slightly different platform sets — do not assume they are identical:

• get_comments: bluesky, facebook, instagram, linkedin, threads, tiktok, twitter, youtube (has threads, no reddit).
• add_comment: bluesky, facebook, instagram, linkedin, reddit, tiktok, twitter, youtube (has reddit, no threads).
• reply_comment: bluesky, facebook, instagram, linkedin, tiktok, twitter, youtube (no reddit, no threads, no snapchat).

Not every network in your post's platforms supports comment operations — surface the limitation rather than retrying.

Function table

Tool	Purpose	Method + Endpoint	Required inputs	Optional inputs
mcp__ayrshare__get_comments	Read comments on a post	GET /comments	id	searchPlatformId (bool; id is a Social Post/Comment ID), commentId (bool; with searchPlatformId, id is a Social Comment ID), platform (one of get_comments' platforms above; required when searchPlatformId or commentId)
mcp__ayrshare__add_comment	Add a NEW top-level comment to a post	POST /comments	id, comment (text; @mentions inline)	platforms (subset of add_comment's platforms above), searchPlatformId (bool; requires exactly one platform), mediaUrls (exactly 1 URL; FB/LinkedIn/X only)
mcp__ayrshare__reply_comment	Reply to an EXISTING comment	POST /comments/reply	commentId (Ayrshare Comment ID, or Social Comment ID if searchPlatformId), comment, platforms (reply_comment's platforms above — bluesky, facebook, instagram, linkedin, tiktok, twitter, youtube; note: no reddit; exactly one if searchPlatformId)	searchPlatformId (bool), mediaUrls (exactly 1 URL; FB/LinkedIn only), videoId (required for TikTok Social-Comment-ID replies), objResponse (bool)

Field names beyond the core inputs and example payloads are in references/examples.md. Note add_comment posts to /comments (keyed by the post id) while reply_comment posts to /comments/reply (keyed by commentId).

Auth note

These tools authenticate with the account's API key, configured when the MCP server is installed. See ../getting-started/SKILL.md for installation and the full auth model; don't re-derive it here. Profile scoping is the profileKey tool argument or the per-connection Profile-Key header (the argument wins when both are set). With neither, calls operate under the account's primary/Business profile.

Usage guidance

• add_comment vs reply_comment — pick by target, not by wording. A NEW top-level comment ON A POST is add_comment (needs the post id). A reply to an EXISTING comment is reply_comment (needs that comment's commentId). "Reply to the post" usually means a top-level comment → add_comment; "reply to that person/commenter" means reply_comment. When unsure, call mcp__ayrshare__get_comments first to see the comment thread and grab the right commentId.
• Read before you write. To respond to a specific comment, mcp__ayrshare__get_comments gives you the comment ids and text. Don't guess a commentId.
• Match the profile to the post. Comment on a post under the same profile that owns it: pass that profile's profileKey argument (or use the matching Profile-Key connection). Commenting under the primary/Business profile on a client's post (or vice versa) targets the wrong identity.
• mediaUrls is restricted. Both accept at most one media URL. add_comment supports it on Facebook, LinkedIn, and X (twitter); reply_comment supports it on Facebook and LinkedIn only (not X).
• TikTok Social-Comment-ID replies need videoId. When replying to a TikTok comment by its Social Comment ID (searchPlatformId), reply_comment also requires videoId.

Gotchas

• add_comment vs reply_comment confusion — the #1 mistake. mcp__ayrshare__add_comment adds a brand-new comment on the post itself (keyed by post id, POST /comments); mcp__ayrshare__reply_comment responds to one existing comment (keyed by commentId, POST /comments/reply). Using the wrong one posts your text in the wrong place. Read the thread with mcp__ayrshare__get_comments if the target isn't obvious.
• Comments are platform-dependent — not every network supports them. Comment create/read/reply availability varies by platform; the supported networks differ per tool (see Supported platforms above — e.g. get_comments allows threads but not reddit, while add_comment allows reddit but not threads), and a network in your post's platforms may still not accept a given comment operation. Don't assume a comment tool works everywhere a post does. Surface the platform limitation rather than retrying.
• searchPlatformId changes what id/commentId means. With searchPlatformId, id/commentId are NATIVE Social IDs rather than Ayrshare IDs, and exactly one platform must be supplied (platform on get_comments, one entry in platforms on add_comment/reply_comment).
• On failure, explain — don't auto-retry. When any comment tool errors, call mcp__ayrshare__explain_error to translate the API error to plain language, then surface it. Never auto-retry add/reply on a 4xx — a 4xx means bad input, an unsupported platform, or a missing comment; retrying a comment write can double-post. A 429 gets at most one retry after a short delay. (Mirror of the global retry-safety rule — full version in getting-started.) Poll get_comments no more than once every 10 minutes.