Skip to main content
Glama

Moderate Comments & Viral Auto-Plug

comments_moderate
Idempotent

List, reply to, hide, or delete public comments on published Instagram posts and Threads replies (live Meta Graph API), or configure an automated viral Auto-Plug reply (auto_plug) that triggers when a post crosses a specified like threshold. Use this tool to engage commenters, remove spam on X/LinkedIn/Instagram/YouTube, or automatically plug a newsletter or product URL underneath high-performing posts. Returns moderation execution status or the active Auto-Plug rule configuration.

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": {
      "action": "<action>"
    },
    "name": "comments_moderate"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesComment moderation action on the connected Instagram (comments) or Threads (replies) account: 'list_posts' recent posts, 'list' comments on a post, 'reply' publicly to a comment, 'hide'/'unhide', 'delete' (Instagram only), or 'auto_plug' to attach an automatic threshold-triggered reply.
postIdNoTarget social post identifier (`post_...`) whose comments are being listed, moderated, or configured for Auto-Plug.
platformNoNetwork whose comments to moderate (default 'instagram').
accountIdNoConnected account id (`acc_...`); defaults to the first live account of `platform`.
commentIdNoSpecific comment identifier (`cmt_...`) when replying to, hiding, or deleting an individual comment.
profileIdNoBrand profile identifier (`prof_...`) that owns the social post and comments.prof_allometrik
replyTextNoPublic reply message text when `action` is 'reply'.
externalPostIdNoPlatform media id (Instagram media id / Threads post id). Alternative to a Nuntior `postId`.
autoPlugMessageNoCall-to-action comment text (e.g. link to docs, newsletter, or product page) automatically posted once the post reaches `autoPlugTriggerLikes`.
autoPlugTriggerLikesNoLike count threshold (e.g. 25 or 50 likes) that triggers Nuntior to automatically publish `autoPlugMessage` as a follow-up comment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / accountId
      Added value: +{
      +  "description": "Connected account id (`acc_...`); defaults to the first live account of `platform`.",
      +  "type": "string"
      +}
    • changedInput schema / properties / action / description
      Previous value: -"Comment moderation action: 'list' comments on a post, 'reply' publicly to a comment, 'hide' or 'delete' spam/abusive comments, or 'auto_plug' to attach an automatic threshold-triggered reply."New value: +"Comment moderation action on the connected Instagram (comments) or Threads (replies) account: 'list_posts' recent posts, 'list' comments on a post, 'reply' publicly to a comment, 'hide'/'unhide', 'delete' (Instagram only), or 'auto_plug' to attach an automatic threshold-triggered reply."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "reply",
      -  "hide",
      -  "delete",
      -  "auto_plug"
      -]New value: +[
      +  "list",
      +  "list_posts",
      +  "reply",
      +  "hide",
      +  "unhide",
      +  "delete",
      +  "auto_plug"
      +]
    • addedInput schema / properties / externalPostId
      Added value: +{
      +  "description": "Platform media id (Instagram media id / Threads post id). Alternative to a Nuntior `postId`.",
      +  "type": "string"
      +}
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "Network whose comments to moderate (default 'instagram').",
      +  "enum": [
      +    "instagram",
      +    "threads"
      +  ],
      +  "type": "string"
      +}
  2. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / action / description
      Added value: +"Comment moderation action: 'list' comments on a post, 'reply' publicly to a comment, 'hide' or 'delete' spam/abusive comments, or 'auto_plug' to attach an automatic threshold-triggered reply."
    • addedInput schema / properties / autoPlugMessage / description
      Added value: +"Call-to-action comment text (e.g. link to docs, newsletter, or product page) automatically posted once the post reaches `autoPlugTriggerLikes`."
    • addedInput schema / properties / autoPlugTriggerLikes / description
      Added value: +"Like count threshold (e.g. 25 or 50 likes) that triggers Nuntior to automatically publish `autoPlugMessage` as a follow-up comment."
    • addedInput schema / properties / commentId / description
      Added value: +"Specific comment identifier (`cmt_...`) when replying to, hiding, or deleting an individual comment."
    • addedInput schema / properties / postId / description
      Added value: +"Target social post identifier (`post_...`) whose comments are being listed, moderated, or configured for Auto-Plug."
    • addedInput schema / properties / profileId / default
      Added value: +"prof_allometrik"
    • addedInput schema / properties / profileId / description
      Added value: +"Brand profile identifier (`prof_...`) that owns the social post and comments."
    • addedInput schema / properties / replyText / description
      Added value: +"Public reply message text when `action` is 'reply'."
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Adds real context beyond annotations: live Meta Graph API calls, automatic threshold-triggered publishing, and what the response contains. However, it never warns that 'delete' is irreversible or that actions require a connected live account, and the annotations already declare the safety profile (destructiveHint=false, openWorldHint=true).

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

Conciseness3/5

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

Front-loaded with the concrete action set and sized reasonably at three sentences. The middle sentence listing unsupported platforms (X/LinkedIn/YouTube) is wasted and actively misleading space that should have been spent on constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Correctly states what is returned (moderation status or active Auto-Plug config), covering the lack of an output schema. But for a write-capable, open-world tool with 10 parameters, the description omits preconditions (connected account, ownership), irreversibility of delete, and the platform scope mismatch.

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 the schema already documents all ten parameters including enums and defaults. The description only echoes the auto_plug/threshold concept, adding no formats, constraints, or parameter interactions beyond the schema.

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?

Names specific verbs (list, reply, hide, delete, configure) and resources (Instagram comments, Threads replies, Auto-Plug rule), making the tool distinguishable from generic post/media siblings. The clarity is undercut by claiming it removes spam on 'X/LinkedIn/Instagram/YouTube' when the schema only permits instagram/threads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives engagement scenarios ('engage commenters', 'remove spam', 'plug a newsletter') but no when-not-to-use guidance and no routing to siblings such as inbox_messages or posts_manage. The stated use cases also contradict the actual supported platforms, which could mislead an agent into calling it for X or LinkedIn content.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources