Benchmark competitor Facebook page engagement
Pull posts from public Facebook pages as JSON with text, reactions, comment and share counts and date, to compare what content wins for you and rivals.
You post three times a week and do not know whether 400 reactions is good. The answer is what competitors in your field get on similar posts, and Facebook shows that one page at a time. Lovely Router reads the pages for you. Send public page links, get one JSON object per post, pay per post from a prepaid balance. Call it from a script, a dashboard job or an AI agent with one API key.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Benchmark competitor Facebook page engagement. Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <the inputs (links, keywords or accounts) and how many results you need>How it works
Pick the pages
Your own page and the pages of the five to ten competitors or peers you want to compare.
Run the tool with a cap
Send the links in
urlswithcountandmax_results. The run holds its maximum cost from your balance and returns the posts as JSON.Compare the numbers
Average reactions, comments and shares per post by page and by month, and read the posts at the top.
Get Facebook page posts with one request
Get Facebook page posts takes public page or group links in urls. count is the total number of posts:
curl https://lovelyrouter.com/v1/tools/facebook-posts/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{
"input": {
"urls": [
"https://www.facebook.com/humansofnewyork/"
],
"count": 10
},
"max_results": 10
}'scrapeUntil keeps only posts newer than a date in YYYY-MM-DD, and sortType is most_relevant, recent_activity or new_posts. A run still going after 60 seconds returns 202; Run a tool shows how to poll.
What each post holds
| Field group | What you get |
|---|---|
| Content | Post text and photos |
| Engagement | Reactions, comments and shares counts |
| Timing | Post date |
Pages have different audience sizes, so compare engagement per post against each page's own average, not raw counts across pages.
Recipes
Pull the last 50 posts from eight peers and compute the median reactions and shares per post, then compare your own page.
Rank a competitor's posts by shares and ask a model what the top ten have in common.
Run weekly with scrapeUntil set to the last run's date, and check whether a rival's posting rate or engagement jumps.
Group posts by weekday and see when peers get the most reactions.
Run the same pages monthly and build the comparison table for an agency report.
Prefer plain words? Connect the MCP server and tell Claude Code or Cursor: "Read the last 30 posts from each of the six Facebook pages in pages.txt, and give me a table of median reactions, comments and shares per page. Set max_results to 180."
What you pay
You pay per post: starting a run holds its maximum cost, the per-call fee plus the per-post fee times max_results, and the run settles to what it returned. The rest of the hold goes back to your balance. A run that fails or times out pays only for the posts it delivered, and a run refused at the start costs nothing.
Reading 50 posts per page for 8 pages is billed as 400 posts. There is no subscription and no monthly minimum: top up from $5, and one balance pays for tools and models. The card above shows today's price; pricing lists every tool.
Frequently asked questions
Can I read posts from a group?+
Yes, the tool accepts page or group links in urls. For groups there is also a dedicated tool: facebook-groups.
Can I limit by date?+
Yes. Set scrapeUntil to a YYYY-MM-DD date and only newer posts are returned.
What do I get for engagement?+
Reactions, comments and shares counts per post.
Do I need a Facebook account?+
No. You send links and an API key.
Do I need a subscription?+
No. You add credit to a prepaid balance and each run draws it down. Nothing renews automatically.
More on the same theme: social listening, influencer research and the tool catalog.