Skip to main content
Glama
Instagram Campaign MCP

Instagram Campaign MCP

by enimarix

hide_comment

Idempotent

Hide or unhide an Instagram comment by comment ID, providing a reversible moderation alternative to permanent deletion.

Instructions

Hide (or unhide) a comment. Reversible, unlike delete.

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

Input Schema

NameRequiredDescriptionDefault
hideNo
comment_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, non-destructive, idempotent operation. The description adds useful behavioral context by stating that hiding is reversible, which is more specific than destructiveHint=false. It does not mention permissions or rate limits, but annotations cover the core safety profile.

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 two short sentences, front-loads the operation, and adds only useful contrast with delete. There is no filler or redundant wording.

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?

This is a simple two-parameter mutation with an output schema and detailed annotations, so the description does not need to explain return values. However, with 0% schema description coverage, the missing parameter semantics and lack of permission context leave meaningful gaps for an agent invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of explaining parameters. It only hints at a hide/unhide toggle and never explains that hide=false performs the unhide, nor does it clarify the required comment_id parameter beyond its self-explanatory name.

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 names a specific verb and resource: 'Hide (or unhide) a comment.' It also explicitly contrasts the operation with delete, so an agent can distinguish it from the sibling delete_comment tool without opening the schema.

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?

The description names the key alternative, delete, and gives the tradeoff: this operation is reversible while delete is not. It does not spell out permissions or explicitly say when permanent deletion is preferable, but the main selection context is clear.

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