Facebook Scraper3 MCP Server

page_reviews

Extract reviews from Facebook pages to analyze customer feedback and ratings. Use this tool to retrieve review data for business insights and monitoring.

Instructions

Get page reviews. Use cursor to get next page

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 8, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pagination ('Use cursor to get next page'), which adds some context about data retrieval behavior. However, it doesn't address critical aspects like rate limits, authentication requirements, error conditions, or what constitutes a 'page review' versus other content types.

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

Conciseness5/5

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

The description is extremely concise with just two short sentences that each serve distinct purposes: stating the core function and providing pagination guidance. There's zero wasted text, and the information is front-loaded appropriately.

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 no parameters, no annotations, and no output schema, the description provides basic functionality and pagination context. However, for a data retrieval tool, it should ideally clarify what 'reviews' means in this context and what format/scope the data returns, especially with many sibling tools that might overlap in functionality.

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 baseline is 4. The description adds value by mentioning cursor-based pagination, which provides context about how to navigate results even though no explicit parameters exist in the schema.

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's purpose as 'Get page reviews', which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'page_details' or 'page_posts', leaving ambiguity about what specifically distinguishes this tool from other page-related operations.

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

Usage Guidelines2/5

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

The description provides minimal guidance with 'Use cursor to get next page', which hints at pagination usage but doesn't explain when to use this tool versus alternatives like 'page_details' or 'page_posts'. No explicit when/when-not guidance or sibling tool comparisons are provided.

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