ScrapeCreators MCP Server

Profile Reels

facebook_profile_reels

Retrieve up to 10 reels from a public Facebook page for research, including video, views, music, and pagination; paid calls need confirm=true.

Instructions

Fetches up to 10 reels per request from a public Facebook page. Each reel includes id, url, view_count, description, creation_time, video_url, thumbnail, play_time_in_ms, and music details. Pagination requires passing both next_page_id and cursor from the previous response. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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": {
      "url": "<url>"
    },
    "name": "facebook_profile_reels"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Facebook page URL
`cursor`	No	To paginate through to the next page
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.
`next_page_id`	No	To paginate through to the next page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations alone (readOnlyHint=false, idempotentHint=false) would look alarming, and the description resolves it by disclosing that it consumes paid API credits, requires confirm=true, and that 'read-like POST requests do not publish to social platforms.' It also enumerates the returned field set, which matters since there is no output schema.

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?

Front-loads what it fetches, then return shape, pagination, and cost/auth constraints. The long inline field enumeration is slightly bulky but each clause carries concrete information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return field list, plus pagination mechanics, credit cost, and the confirm requirement. Nothing essential to calling it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3. The description exceeds it by clarifying that pagination requires BOTH next_page_id and cursor from the previous response, a constraint the individual schema fields ('To paginate through to the next page') do not convey.

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

Purpose5/5

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

States a specific verb (fetches), resource (reels), source (a public Facebook page), and scope (up to 10 per request). An agent can distinguish it from facebook_profile_posts and facebook_profile_photos without opening any schema.

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 describes operational conditions (public page, confirm=true, credit consumption) but never says when to prefer this tool over siblings like facebook_profile_posts or instagram_reels. Usage is implied by the resource name rather than explicitly guided.

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

Deploy Server