Facebook Page Photo Gallery & Engagement Scraper: MCP config, n8n workflow and API

This Actor returns a row for each public Facebook photo, including image links, captions, timestamps, reaction breakdowns, comment and share counts, tagged people and source context. An agent should call it to inventory public photo collections or review engagement on photos from pages, profiles and albums.

Supply startUrls with Facebook page, profile, photo-tab, album or single-photo URLs, or bare handles.

Fastest route, in Claude Code:

claude mcp add --transport http facebook-page-photo-gallery-and-engagement-scraper "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper" --name facebook-page-photo-gallery-and-engagement-scraper

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.10 (the start event, $0.10 per GB, times its default 512 MB of memory, billed as 1 GB), $0.03 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.10$0.010$0.11
100$0.10$0.10$0.20
1,000$0.10$0.99$1.09

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http facebook-page-photo-gallery-and-engagement-scraper "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • vexaloom-labs--facebook-page-photo-gallery-and-engagement-s-3070runs the Actor and returns its results
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowfacebook-page-photo-gallery-and-engagement-scraper.n8n.json

Actor on Apify
{
  "name": "Facebook Page Photo Gallery & Engagement Scraper to n8n only",
  "nodes": [
    {
      "id": "604b0d12-1356-49de-a6ca-dd2bcba4d27f",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "3bd92bb2-9fdf-4638-a2b8-ef3d70ac9cbf",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "d89f3be6-436b-47ad-a970-26dc3398acc3",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/vexaloom-labs~facebook-page-photo-gallery-and-engagement-scraper/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"startUrls\": [\n    {\n      \"url\": \"https://www.facebook.com/humansofnewyork/photos\"\n    }\n  ],\n  \"resultsLimit\": 1,\n  \"photoTab\": \"uploaded\",\n  \"includeAlbums\": false,\n  \"includeDetails\": true,\n  \"storeImages\": true\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "d843431a-43aa-4074-a67a-2ced9dafecbb",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Facebook Page Photo Gallery & Engagement Scraper\n\nSource: [vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper](https://apify.com/vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~facebook-page-photo-gallery-and-engagement-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"startUrls":[{"url":"https://www.facebook.com/humansofnewyork/photos"}],"resultsLimit":1,"photoTab":"uploaded","includeAlbums":false,"includeDetails":true,"storeImages":true}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/photos"
    }
  ],
  "resultsLimit": 1,
  "photoTab": "uploaded",
  "includeAlbums": false,
  "includeDetails": true,
  "storeImages": true
}

FieldTypeWhat it does
startUrls required array Facebook page, profile, photos tab, tagged tab, albums tab, album, or single-photo URL. Bare handles such as nasa are accepted too.
resultsLimit integer Global cap across all Start URLs. The actor keeps paginating until this many photos are collected or the source runs out.
newerThan string Only include photos posted on or after this date (YYYY-MM-DD). Applied by Facebook for page and tagged tabs. For albums the actor reads each photo timestamp (even with includeDetails off) and applies the bound; rows…
olderThan string Only include photos posted on or before this date (YYYY-MM-DD). Applied by Facebook for page and tagged tabs. For albums the actor reads each photo timestamp (even with includeDetails off) and applies the bound; rows…
photoTab string (2 options) For page and profile URLs: photos uploaded by the page, or photos where the page is tagged by others. Ignored for album and photo URLs.
includeAlbums boolean For page and profile URLs, also walk every album listed on the page's Albums tab and collect its photos. A photos_albums URL implies this automatically.
includeDetails boolean Open each photo to add its caption, timestamp, reactions, comments, shares, tagged people, owner, album, and post link. Turn off for a fast grid-only export; album date bounds still read only the timestamp needed for…
storeImages boolean Copy each full-size image and thumbnail to Apify storage and return non-expiring URLs. The signed Facebook originals and their expiry are kept in the record.

What your agent receives

Each run returns a list of records. The Actor publishes 44 fields, starting with photoId, photoUrl, imageUrl, thumbnailUrl.

FieldWhat it holdsFormat
photoIdPhoto IDtext
photoUrlPhoto URLlink
imageUrlImagelink
thumbnailUrlThumbnaillink
captionCaptiontext
pageNamePagetext
timestampPostedtext
reactionsTotalReactionsnumber
commentsCountCommentsnumber
shareCountSharesnumber
30 more fields
FieldWhat it holdsFormat
imageUrlOriginalImage (original)link
imageExpiresAtImage expirestext
imageWidthWidthnumber
imageHeightHeightnumber
thumbnailUrlOriginalThumbnail (original)link
altTextAlt texttext
ocrTextOCR text (alt text)text
createdTimeCreated (Unix)number
likesCountReactions totalnumber
likeCountLikenumber
loveCountLovenumber
careCountCarenumber
hahaCountHahanumber
wowCountWownumber
sadCountSadnumber
angryCountAngrynumber
reactionsByTypeReactions by typeobject
taggedPeopleTagged peoplearray
authorNameAuthortext
authorUrlAuthor URLlink
uploaderIdUploader IDtext
uploaderNameUploadertext
uploaderUrlUploader URLlink
pageIdPage IDtext
pageUrlPage URLlink
pageFollowersPage followersnumber
albumIdAlbum IDtext
albumNameAlbumtext
postIdPost IDtext
postUrlPost URLlink

4 more fields in the full output.

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdfacebook-page-photo-gallery-and-engagement-scraper/SKILL.md

---
name: facebook-page-photo-gallery-and-engagement-scraper
description: "One row per public Facebook photo with image and thumbnail links, caption, timestamp, reaction breakdown, comments, shares, tagged people, owner/page/album/post context, and source metadata. Runs the Apify Actor vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper. Use when the user needs Facebook data with fields such as photoId, photoUrl, imageUrl, thumbnailUrl, caption, pageName and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper"
  store-url: "https://apify.com/vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper"
---

# Facebook Page Photo Gallery & Engagement Scraper

Use this skill to fetch Facebook data with the Apify Actor `vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `startUrls` | array, required | Facebook page, profile, photos tab, tagged tab, albums tab, album, or single-photo URL. Bare handles such as nasa are accepted too. |
| `resultsLimit` | integer | Global cap across all Start URLs. The actor keeps paginating until this many photos are collected or the source runs out. |
| `newerThan` | string | Only include photos posted on or after this date (YYYY-MM-DD). Applied by Facebook for page and tagged tabs. For albums the actor reads each photo timestamp (even with includeDetails off) and applies the bound; rows stay grid-only. |
| `olderThan` | string | Only include photos posted on or before this date (YYYY-MM-DD). Applied by Facebook for page and tagged tabs. For albums the actor reads each photo timestamp (even with includeDetails off) and applies the bound; rows stay grid-only. |
| `photoTab` | one of `uploaded`, `tagged` | For page and profile URLs: photos uploaded by the page, or photos where the page is tagged by others. Ignored for album and photo URLs. |
| `includeAlbums` | boolean | For page and profile URLs, also walk every album listed on the page's Albums tab and collect its photos. A photos_albums URL implies this automatically. |
| `includeDetails` | boolean | Open each photo to add its caption, timestamp, reactions, comments, shares, tagged people, owner, album, and post link. Turn off for a fast grid-only export; album date bounds still read only the timestamp needed for filtering. |
| `storeImages` | boolean | Copy each full-size image and thumbnail to Apify storage and return non-expiring URLs. The signed Facebook originals and their expiry are kept in the record. |

Example `input.json` (the Actor's published prefill):

```json
{
  "startUrls": [
    {
      "url": "https://www.facebook.com/humansofnewyork/photos"
    }
  ],
  "resultsLimit": 1,
  "photoTab": "uploaded",
  "includeAlbums": false,
  "includeDetails": true,
  "storeImages": true
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~facebook-page-photo-gallery-and-engagement-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/vexaloom-labs~facebook-page-photo-gallery-and-engagement-scraper/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `photoId`, `photoUrl`, `imageUrl`, `thumbnailUrl`, `caption`, `pageName`, `timestamp`, `reactionsTotal`, `commentsCount`, `shareCount`, `imageUrlOriginal`, `imageExpiresAt`, `imageWidth`, `imageHeight`, `thumbnailUrlOriginal`, `altText`, `ocrText`, `createdTime`, `likesCount`, `likeCount`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.

  • Claude Code: save it as ~/.claude/skills/facebook-page-photo-gallery-and-engagement-scraper/SKILL.md, or .claude/skills/facebook-page-photo-gallery-and-engagement-scraper/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/facebook-page-photo-gallery-and-engagement-scraper/SKILL.md, or .agents/skills/facebook-page-photo-gallery-and-engagement-scraper/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill facebook-page-photo-gallery-and-engagement-scraper
  • Set APIFY_TOKEN in the agent's environment.

Good jobs for this Actor

  • Build a photo inventory with imageUrl, thumbnailUrl, caption and altText.
  • Compare photo engagement using reactionsTotal, reactionsByType, commentsCount and shareCount.
  • Collect photos within a publication window using newerThan and olderThan.
  • Copy full-size images and thumbnails to Apify storage with storeImages for later retrieval.

Prompts to try

  • Collect photos from https://www.facebook.com/humansofnewyork/photos using startUrls with includeDetails enabled, then list captions, reaction totals and photo URLs.
  • Use startUrls with the bare handle nasa, enable includeAlbums and storeImages, and build an inventory with image links and dimensions.
  • Collect photos from https://www.facebook.com/humansofnewyork/photos with photoTab set to tagged and includeDetails enabled, then summarize taggedPeople, authorName and shareCount.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

Can the returned image links expire?

The signed Facebook originals can expire, and imageExpiresAt records their expiry. Enabling storeImages copies full-size images and thumbnails to Apify storage and returns non-expiring URLs.

What does includeDetails add?

includeDetails opens each photo to collect its caption, timestamp, reactions, comments, shares, tagged people, owner, album and post link. Turn it on when the workflow needs those details alongside image links.

Does resultsLimit apply separately to each source?

resultsLimit is a global cap across all startUrls. The Actor keeps paginating until it reaches that cap or the source runs out of photos.

How do I connect Facebook Page Photo Gallery & Engagement Scraper to Claude?

In Claude Code run: claude mcp add --transport http facebook-page-photo-gallery-and-engagement-scraper "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/facebook-page-photo-gallery-and-engagement-scraper and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Facebook Page Photo Gallery & Engagement Scraper need?

The published input schema requires startUrls. The example on this page uses the Actor's own Store prefill.

What does Facebook Page Photo Gallery & Engagement Scraper cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, vexaloom-labs--facebook-page-photo-gallery-and-engagement-s-3070, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run. Apify's MCP server listed them for this exact URL on 2026-11-11.