Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

post_comments_list

Read-onlyIdempotent

Retrieve comments on a Facebook Page post and choose top-level or full threaded streams with pagination, chronological ordering, and field selection.

Instructions

List comments on a post List comments on a post. Defaults to top-level comments; set filter=stream for the full threaded stream, order=chronological_ascending to read oldest first. Graph API: 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>"
    },
    "name": "post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
orderNo
fieldsNo
filterNo
post_idYes
access_tokenNoOptional Facebook Page access token for this call only. Use it when the token you hold is not the one this server was configured with, or when the configured token has expired. Takes effect for this call and nothing else. Also accepted as token or page_token.
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered elsewhere. The description adds genuine value by disclosing the default scoping behavior (top-level only) and how to expand to a full threaded stream, which the annotations cannot convey. It says nothing about pagination behavior or token requirements beyond the schema's access_token note.

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

Conciseness3/5

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

The core sentence is front-loaded and information-dense, but the description literally repeats itself ("List comments on a post List comments on a post."), which is wasted tokens. The parameter guidance sentence is efficient.

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?

An output schema exists, so return values need not be described, and the mode-switching guidance covers the most consequential choices. Still, for an 8-parameter tool with 13% schema coverage, key inputs (pagination, fields selection) are left for the agent to guess.

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 only 13%, so the description must carry weight; it does add meaning for filter and order by naming valid values and their effect. However, after, limit, fields and extra_fields are undocumented in both schema and description, leaving half the surface unexplained. This is above the 0% baseline but well short of compensating for the coverage gap.

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

Purpose4/5

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

States a clear verb+resource ("List comments on a post") and even names the underlying Graph API endpoint, GET {post_id}/comments, so the agent knows exactly which operation is performed. It does not differentiate from siblings such as conversation_messages_list, which contextually appears to be a different resource.

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

Usage Guidelines3/5

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

Gives useful default guidance ("Defaults to top-level comments") and tells when to switch modes via filter=stream and order=chronological_ascending. It stops short of saying when to choose this tool over any alternative or listing prerequisites such as required permissions.

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