Skip to main content
Glama
pauloFroes

mcp-meta-inbox

by pauloFroes

Hide Comment

hide_comment
Idempotent

Hide or unhide a comment to make it invisible to everyone except the author and their friends, providing a reversible alternative to deletion for moderating spam or abuse.

Instructions

Hide or unhide someone else's comment. A hidden comment stays visible to its author and their friends but disappears for everyone else — the reversible alternative to delete_comment for spam or abuse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hideNotrue hides the comment, false unhides it.
platformNoWhich platform the ID belongs to. Leave unset to auto-detect from the ID shape: Facebook IDs are compound ("{page}_{object}"), Instagram IDs are a flat run of digits.
comment_idYesComment ID to hide or unhide.
Behavior4/5

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

Describes visibility behavior (visible to author and friends, hidden from others) and reversibility, adding context beyond annotations which already indicate non-destructive, idempotent, non-read-only nature. Does not mention authentication or rate limits but is sufficient.

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?

Two sentences, front-loaded with purpose and key distinction, every word adds value.

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?

Given good annotations, high schema coverage, and clear description, it is mostly complete. No output schema, but tool likely returns simple success; minor gap but acceptable.

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 100% and description adds minimal extra: explains platform auto-detection logic slightly different from schema but already present. Baseline 3 for high coverage.

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?

Clear verb 'hide or unhide' with specific resource 'someone else's comment'. Distinguishes itself from sibling delete_comment by highlighting reversible nature.

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?

Explicitly states it is the reversible alternative to delete_comment for spam/abuse, providing clear context on when to use vs. delete_comment.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pauloFroes/mcp-meta-inbox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server