Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook post or reel comments

facebook_post_comments_list
Read-onlyIdempotent

Retrieve comments from a Facebook post or Reel by URL and paginate with a cursor to collect every comment.

Instructions

List comments on a Facebook post or Reel by URL. Optional inputs: url, cursor and feedbackId. Returns a list (use cursor when paginated).

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_post_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoLink to the Facebook post or reel whose comments should be listed.
cursorNoOpaque cursor from a previous response to fetch the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
feedbackIdNoOptional Facebook feedback identifier for the target post; when available it can improve lookup performance.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds two useful behavioral facts beyond that: the return shape ('Returns a list') and the cursor-based pagination model. It omits page-size limits, ordering of comments, and rate-limit behavior for an open-world scraper-style call.

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

Conciseness4/5

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

Three short sentences, front-loaded with the core action and ending with the pagination mechanic. No filler. It loses a point only because the 'Optional inputs' enumeration partially duplicates what the schema already states for all six parameters.

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?

For a 6-parameter, no-output-schema read tool, the description covers the action, the return shape and pagination, which is the essential core. It leaves unaddressed the optional/required confusion around `url`, the feedbackId performance tradeoff, and how this differs from the replies sibling — enough gaps to keep it at minimum viable rather than complete.

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 every parameter is already documented in the schema and the baseline is 3. The description names url, cursor and feedbackId, but calling `url` an 'optional input' sits awkwardly against the opening claim that comments are listed 'by URL' — an agent may wonder what happens with no URL supplied.

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 specific verb and resource ('List comments on a Facebook post or Reel') plus the identifying input ('by URL'), which is enough to distinguish it from generic post tools like facebook_post_get. It does not, however, distinguish it from the close sibling facebook_post_comments_replies_list, leaving the top-level-vs-reply boundary ambiguous.

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?

The only usage instruction is the pagination hint ('use cursor when paginated'), which is genuinely useful. There is no guidance on when to prefer this over the replies tool, no prerequisite/auth context, and no statement about what happens if the URL points to a non-Facebook resource.

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