mcp-meta-inbox

Create Comment

create_comment

Post a new top-level comment on a Facebook post under the Page's name. Confirm the text before publishing.

Instructions

Post a new top-level comment on your own Facebook post. This publishes publicly under the Page's name — confirm the text with a human first. Instagram does not allow creating top-level comments via the API; use reply_to_comment there.

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": {
      "object_id": "<object_id>",
      "message": "<message>"
    },
    "name": "create_comment"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes	Comment text.
`object_id`	Yes	Facebook post ID to comment on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false, destructiveHint=false, etc. The description adds important context: the comment publishes publicly under the Page's name and requires human confirmation. It also discloses the Instagram limitation. This adds value beyond annotations, though it could mention rate limits or auth requirements.

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 concise sentences that front-load the core purpose and then add critical usage and exclusion details. Every sentence contributes meaningfully with no redundancy.

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

Completeness5/5

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

Given only two simple parameters and no output schema, the description covers purpose, behavioral implications, platform restrictions, and safety guidance. It is fully sufficient for an agent to decide when and how to invoke this tool correctly.

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

Parameters4/5

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

Schema coverage is 100% with clear descriptions for both parameters. The description adds context that object_id refers to a Facebook post and message is the comment text. While it doesn't add new parameter details beyond schema, the usage context ('own Facebook post') enriches understanding.

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 clearly states the action ('Post a new top-level comment') and the specific resource ('your own Facebook post'). It uniquely distinguishes from sibling tools like reply_to_comment by specifying top-level versus reply, and notes the Instagram restriction.

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 tells when to use (on own Facebook post) and when not to (Instagram does not allow top-level comments). Includes a safety guideline to confirm text with a human first, providing clear context for appropriate usage.

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

Deploy Server