Skip to main content
Glama
Sign In
mcp-meta-inbox

mcp-meta-inbox

by pauloFroes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get Comment

get_comment
Read-only

Retrieve a comment's author, timestamp, and moderation flags by ID to check content before hiding or deleting.

Instructions

Read a single comment by ID, with its author, timestamp and moderation flags (can_hide / can_remove on Facebook, hidden on Instagram). Call this before hiding or deleting so the decision is made on the real text.

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": "get_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated fields. Platform-specific default.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds value by detailing the returned data (author, timestamp, moderation flags) and noting platform-specific differences in flags (can_hide/can_remove vs. hidden). No contradictions.

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, each earning its place: first states the core action and returned data, second provides critical usage guidance. No filler or redundancy.

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?

No output schema exists, but the description compensates by naming specific return fields (author, timestamp, moderation flags). However, it omits any mention of error states (e.g., comment not found) or whether additional fields are returned. Still adequate for a simple read tool.

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 each parameter is already documented in the schema. The tool description does not add further meaning beyond the schema; it merely references the auto-detection behavior already described in the platform parameter's schema description. Thus baseline score of 3.

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?

Explicitly states it reads a single comment by ID and returns author, timestamp, and moderation flags. Clearly distinguishes from sibling tools like list_comments, hide_comment, and delete_comment by specifying it's the read-before-modification step.

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?

Provides explicit guidance: 'Call this before hiding or deleting so the decision is made on the real text.' Also explains platform auto-detection behavior, giving clear context on when to use and what not to skip.

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

Deploy Server

Other Tools