Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Facebook comment replies

facebook_post_comments_replies_list
Read-onlyIdempotent

Lists replies to a Facebook comment from a provided cursor and returns paginated results, enabling review or continuation of comment threads.

Instructions

List replies to a Facebook comment. Requires cursor. 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": {
      "cursor": "<cursor>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_post_comments_replies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorYesComment `repliesCursor` from post comments, or `page.nextCursor` to paginate replies.
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.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds the cursor requirement and that pagination is cursor-driven, which is modest extra context, but says nothing about ordering, page size, or empty-result behavior.

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, front-loaded sentences with the key prerequisite first. The parenthetical '(use cursor when paginated)' slightly restates the prior sentence, but overall it is tight and free of padding.

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 simple read-only list tool with complete schema coverage and annotations, the essentials are present. However, with no output schema, the description does not indicate what a reply record contains or how pagination terminates, leaving a small but real gap.

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 coverage is 100%, so all four parameters including cursor, context, llm_model and conversation_id are already documented in the schema. The description restates the cursor requirement without adding syntax or sourcing detail beyond what the schema's cursor text provides; baseline 3 is appropriate.

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?

The description names a specific verb and resource ('List replies to a Facebook comment'), which is distinguishable from the parent-comment siblings such as facebook_post_comments_list by the word 'replies'. It does not explicitly name the alternative tool, but the resource scope is unambiguous.

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?

It states a hard prerequisite ('Requires `cursor`') and hints at pagination, but gives no guidance on when to choose this over other reply-listing tools or when not to call it. Usage is implied rather than explained.

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