Facebook Scraper3 MCP Server

search_groups_posts

Search Facebook groups for posts to extract relevant content and discussions. This tool helps users find specific information within group conversations by querying posts across Facebook groups.

Instructions

Searches group for posts

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": "search_groups_posts"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 8, 2026

TDQS

D1.9/5.0

Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe any traits: it doesn't specify if this is a read-only or mutating operation, what the search scope or limitations are, authentication needs, rate limits, or output format. This leaves critical behavioral aspects undocumented.

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 description is concise ('Searches group for posts') but under-specified, not efficiently front-loaded with useful information. While it avoids verbosity, it fails to earn its place by adding value beyond the tool name, making it inefficient rather than appropriately sized.

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 implied by 'search' functionality, lack of annotations, no output schema, and multiple sibling tools, the description is incomplete. It doesn't explain what 'search' means, how results are returned, or differentiate from similar tools, making it inadequate for effective tool selection and invocation.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is acceptable here. A baseline of 4 is appropriate as the schema fully handles the parameter semantics without requiring compensation from the description.

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 'Searches group for posts' restates the tool name 'search_groups_posts' almost verbatim, making it tautological. It lacks specificity about what 'search' entails (e.g., keyword-based, filter-based) and doesn't differentiate from sibling tools like 'get_group_posts' or 'search_post', leaving the purpose vague beyond the obvious.

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 guidance is provided on when to use this tool versus alternatives. With sibling tools like 'get_group_posts' (likely for listing) and 'search_post' (likely broader search), the description offers no context, exclusions, or prerequisites, leaving the agent with no usage direction.

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