Skip to main content
Glama

Social0

moderate_comment

Destructive

Like, unlike, or hide a comment. Hiding is Instagram and Facebook Pages only. Requires publication_id from list_inbox_comments. Hiding is a moderation action — confirm with the user first.

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": {
      "comment_id": "<comment_id>",
      "publication_id": "<publication_id>",
      "action": "<action>"
    },
    "name": "moderate_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
comment_idYesComment ID from list_inbox_comments
publication_idYespublication_id from the same comment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and non-idempotent, and the description adds context beyond them: the hide action is a moderation operation requiring user confirmation and is unsupported outside Instagram and Facebook Pages. It does not explain what state changes on like/unlike or whether hiding is reversible, which is the remaining behavioral gap.

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?

Three short sentences, each carrying a distinct fact: the action set, the platform restriction, the provenance requirement, and the confirmation rule. Nothing is repeated and the constraint most likely to block a call is placed early.

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 three-parameter mutation tool with no output schema, this covers the key risks: destructive confirmation, platform scoping, and the upstream dependency on list_inbox_comments. It would be complete with a note on what a successful like/unlike returns or how failures surface.

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 coverage is 67% and the enum plus both ID parameters are already described structurally. The description only adds one meaningful constraint, that hide is platform-limited, but does not clarify what 'same comment' means operationally or how to recover if publication_id does not match.

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?

The description names concrete verbs (like, unlike, hide) against a specific resource (a comment), and the action enum in the schema removes ambiguity with reply_to_comment. It does not explicitly name the sibling it differs from, so it falls short of full sibling differentiation.

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

Usage Guidelines4/5

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

It gives real selection criteria: 'Hiding is Instagram and Facebook Pages only' constrains which platform/action combinations are valid, and 'Hiding is a moderation action — confirm with the user first' tells the agent to pause before the destructive branch. It stops short of explaining when to prefer like vs unlike or pointing to reply_to_comment for responses.

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.