ScrapeCreators: Facebook Profile Reels

Fetches up to 10 reels per request from a public Facebook page.

Tool ID: scrapecreators_facebook_profile_reels

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'scrapecreators_facebook_profile_reels',
  {
    "url": "https://example.com"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute scrapecreators_facebook_profile_reels --input '{
  "url": "https://example.com"
}' --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe scrapecreators_facebook_profile_reels --json for the complete live contract.

Input reference

Fetches up to 10 reels per request from a public Facebook page. Each reel includes id, post_id, url, view_count, description, creation_time, video_url, thumbnail, play_time_in_ms, and music details. view_count comes from Facebook’s public Reels badge (play_count_reduced), converted to a number. abbreviated values such as 27K become 27000, not an exact count. This list does not include like_count, reaction_counts, comment_count, share_count, or an is_pinned flag. Do not infer pinning from the order of returned reels. For available engagement metrics and a more precise view_count when Facebook exposes it, call /v1/facebook/post separately with each reel’s returned url. There is no batch detail parameter on this endpoint. The detail view_count can still be null or lower than the public Reels badge. Pagination requires passing both next_page_id and cursor from the previous response. See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.url`	`string`	Yes	—	Facebook page URL
`payload.next_page_id`	`string`	No	—	To paginate through to the next page
`payload.cursor`	`string`	No	—	To paginate through to the next page

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`unknown`	Yes	—	Provider response payload.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0.02 per pricing unit.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation