meta-mcp

List comments on a post

post_comments

Retrieve comments from a Facebook post using post ID and page ID. Supports pagination, field selection, and chronological ordering.

Instructions

GET /{post_id}/comments.

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": {
      "post_id": "<post_id>",
      "via_page_id": "<via_page_id>"
    },
    "name": "post_comments"
  }
}

Input Schema

Name	Required	Description	Default
`post_id`	Yes
`via_page_id`	Yes
`fields`	No
`order`	No
`limit`	No
`auto_paginate`	No
`max_pages`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 10, 2026

TDQS

D1.6/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only implies a read operation via the GET method but lacks details on permissions, rate limits, or pagination behavior. The description is insufficient for a 7-parameter tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but under-specified. It lacks critical details and is not appropriately concise for a tool with 7 parameters and no annotations.

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

Completeness1/5

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

Given the complexity (7 parameters), absent output schema, and no annotations, the description is severely incomplete. It fails to explain return values, parameter usage, or any context needed for effective tool invocation.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain any parameter's meaning, including the required 'post_id' and 'via_page_id' or optional ones like 'fields' and 'order'. The description adds no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GET /{post_id}/comments.' minimally states the HTTP method and endpoint, but does not explicitly state that it lists comments on a post. It is a tautology of the name and title without adding new information or differentiating from siblings.

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

Usage Guidelines1/5

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

No usage guidelines are provided. The description does not indicate when to use this tool versus alternative comment-related tools or other list tools, leaving the agent without guidance.

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