Facebook Scraper3 MCP Server

get_group_posts

Extract posts from public Facebook groups using the Facebook Scraper3 API. Retrieve group content for analysis or monitoring purposes.

Instructions

Get group posts. Only PUBLIC groups can be scrapped! If there are no post response, check if group is not private.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_group_posts"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 8, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It reveals that the tool scrapes data (not API-based) and only works on public groups, which are important behavioral traits. However, it doesn't disclose rate limits, authentication needs, pagination, or what format the posts are returned in.

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?

The description is appropriately brief (two sentences) and front-loaded with the core purpose. The second sentence adds important usage guidance. There's no wasted text, though it could be slightly more structured with bullet points or clearer separation of concerns.

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?

Given the tool has 0 parameters and no output schema, the description provides adequate context about the scraping behavior and public-only restriction. However, for a data retrieval tool, it should ideally mention what data is returned (post content, metadata, etc.) and any limitations like date ranges or result limits.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of parameters. The description doesn't need to add parameter information, and the baseline for this situation is 4 according to the scoring guidelines.

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

Purpose3/5

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

The description states the tool 'Get group posts' which is a clear verb+resource combination, but it doesn't specify what type of posts or how they're retrieved (scraped vs API). It doesn't distinguish from sibling tools like 'get_group_details' or 'search_groups_posts' which might serve similar purposes.

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

Usage Guidelines4/5

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

The description provides explicit guidance about when to use it ('Only PUBLIC groups can be scrapped!') and what to check if there's no response ('check if group is not private'). However, it doesn't mention alternatives like 'search_groups_posts' or 'get_group_details' which might be better for specific use cases.

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