Skip to main content
Glama

SocialAPIs

by io.github.SocialAPIsHub
OverviewDiscussionsAdmin

Facebook: Page

facebook_page
Read-only

Facebook pages: profile details, page ID, posts, videos, reels and photo albums.

Actions:

  • action=details: Get a Facebook page's profile: name, category, follower and like counts, bio, contact info (email, phone, website, address), rating and the ad_page_id used by the Ads Library tools. Use it when you have the page URL; to find a page by name, use facebook_search (action=pages) first. Pricing: 1 credit per call; 5 credits when exact_followers_count=true. Inputs: link (required), exact_followers_count (optional).

  • action=id: Resolve a Facebook page URL to its numeric page ID. Use it when another tool needs a page or profile ID; use action=details for the page's data. Pricing: 1 credit per call. Inputs: link (required).

  • action=posts: List a Facebook page's recent posts, newest first, with text, media, reactions, comment and share counts. Returns 3-9 posts per call plus an end_cursor for the next page; filter by date with after_time / before_time. For reels or videos only, use action=reels or action=videos. Pricing: ceil(posts_returned / 3) credits per call, minimum 1. Inputs: link (required), limit (optional), end_cursor (optional), after_time (optional), before_time (optional), timezone (optional).

  • action=videos: List videos uploaded to a Facebook page, with video_id, title, duration, view count and thumbnail. Provide the page URL (link) or its numeric profile_id. Returns an end_cursor for the next page. For short-form reels, use action=reels. Pricing: 1 credit per call. Inputs: link (optional), profile_id (optional), limit (optional), end_cursor (optional).

  • action=reels: List a Facebook page's reels (short-form videos). Returns an end_cursor for the next page. For long-form videos, use action=videos. Pricing: 1 credit per call. Inputs: link (required), end_cursor (optional).

  • action=albums: List the photo albums of a Facebook page, with album_id, album_title, url, thumbnail_uri and album_items_count (text, e.g. "400 items"). Needs the numeric page ID (profile_id) from action=id. Returns an end_cursor for the next page. To get the photos in an album, pass its album_id to action=album_items. Pricing: 1 credit per call. Inputs: profile_id (required), limit (optional), end_cursor (optional).

  • action=album_items: Get the photos and videos inside a Facebook album (from a page or a group): media_id, media_type, url, thumbnail_uri and timestamp (Unix seconds). Needs an album_id from action=albums or facebook_group (action=albums). Returns an end_cursor for the next page. Pricing: 1 credit per call. Inputs: album_id (required), end_cursor (optional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoFacebook page URL, e.g. https://facebook.com/nike. For videos you can pass profile_id instead. Required for: details, id, posts, reels. Optional for: videos.
limitNoResults per call. posts: 3-9 (default 3) · videos: 6-12 (default 6) · albums: 8-16 (default 8). Optional for: posts, videos, albums.
actionYesWhich operation to run. See the tool description for what each action returns and which parameters it needs.
album_idNoAlbum ID, from action=albums or facebook_group (action=albums). Required for: album_items.
timezoneNoTimezone for timestamps (e.g., UTC, America/New_York). Optional for: posts.
after_timeNoISO 8601 timestamp - only return posts after this time. Optional for: posts.
end_cursorNoPagination cursor from the previous response. Optional for: posts, videos, reels, albums, album_items.
profile_idNoNumeric Facebook page ID, from action=id. For videos, an alternative to link. Required for: albums. Optional for: videos.
before_timeNoISO 8601 timestamp - only return posts before this time. Optional for: posts.
exact_followers_countNoWhen true, performs a deeper scrape to return the exact follower count (e.g. 38,493,217 instead of "38M"). Charges 5 credits when true, 1 credit otherwise. Default: false. Optional for: details.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesJSON response from the SocialAPIs REST endpoint, unchanged. Object or array depending on the endpoint; most include a `meta` block (statusCode, duration, creditsCharged, creditsRemaining).
creditsChargedNoCredits charged for this call, or null if the endpoint did not report it.
creditsRemainingNoCredits left on the API key after this call, or null if not reported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "details",
-  "id",
-  "posts",
-  "videos",
-  "reels"
-]New value: +[
+  "details",
+  "id",
+  "posts",
+  "videos",
+  "reels",
+  "albums",
+  "album_items"
+]
    • addedInput schema / properties / album_id
      Added value: +{
+  "description": "Album ID, from action=albums or facebook_group (action=albums).\nRequired for: album_items.",
+  "type": "string"
+}
    • changedInput schema / properties / end_cursor / description
      Previous value: -"Pagination cursor from the previous response.\nOptional for: posts, videos, reels."New value: +"Pagination cursor from the previous response.\nOptional for: posts, videos, reels, albums, album_items."
    • changedInput schema / properties / limit / description
      Previous value: -"Results per call. posts: 3-9 (default 3) · videos: 6-12 (default 6).\nOptional for: posts, videos."New value: +"Results per call. posts: 3-9 (default 3) · videos: 6-12 (default 6) · albums: 8-16 (default 8).\nOptional for: posts, videos, albums."
    • changedInput schema / properties / limit / maximum
      Previous value: -12New value: +16
    • changedInput schema / properties / profile_id / description
      Previous value: -"Facebook profile ID (alternative to link).\nOptional for: videos."New value: +"Numeric Facebook page ID, from action=id. For videos, an alternative to link.\nRequired for: albums. Optional for: videos."
  2. Changed8 schema fields changed
    • changedInput schema / properties / after_time / description
      Previous value: -"posts (optional): ISO 8601 timestamp - only return posts after this time."New value: +"ISO 8601 timestamp - only return posts after this time.\nOptional for: posts."
    • changedInput schema / properties / before_time / description
      Previous value: -"posts (optional): ISO 8601 timestamp - only return posts before this time."New value: +"ISO 8601 timestamp - only return posts before this time.\nOptional for: posts."
    • changedInput schema / properties / end_cursor / description
      Previous value: -"posts (optional): Pagination cursor for next page of results. videos, reels (optional): Pagination cursor."New value: +"Pagination cursor from the previous response.\nOptional for: posts, videos, reels."
    • changedInput schema / properties / exact_followers_count / description
      Previous value: -"details (optional): When true, performs a deeper scrape to return the exact follower count (e.g. 38,493,217 instead of \"38M\"). Charges 5 credits when true, 1 credit otherwise. Default: false."New value: +"When true, performs a deeper scrape to return the exact follower count (e.g. 38,493,217 instead of \"38M\"). Charges 5 credits when true, 1 credit otherwise. Default: false.\nOptional for: details."
    • changedInput schema / properties / limit / description
      Previous value: -"posts (optional): Maximum number of posts to return. Default: 3. Minimum: 3. Maximum: 9. videos (optional): Maximum number of videos to return. Default: 6. Minimum: 6. Maximum: 12."New value: +"Results per call. posts: 3-9 (default 3) · videos: 6-12 (default 6).\nOptional for: posts, videos."
    • changedInput schema / properties / link / description
      Previous value: -"details, posts, reels (required): Facebook page URL. id (required): Facebook page URL (e.g., https://facebook.com/nike). videos (optional): Facebook page URL."New value: +"Facebook page URL, e.g. https://facebook.com/nike. For videos you can pass profile_id instead.\nRequired for: details, id, posts, reels. Optional for: videos."
    • changedInput schema / properties / profile_id / description
      Previous value: -"videos (optional): Facebook profile ID (alternative to link)."New value: +"Facebook profile ID (alternative to link).\nOptional for: videos."
    • changedInput schema / properties / timezone / description
      Previous value: -"posts (optional): Timezone for timestamps (e.g., UTC, America/New_York)."New value: +"Timezone for timestamps (e.g., UTC, America/New_York).\nOptional for: posts."
  3. Changed8 schema fields changed
    • changedInput schema / properties / after_time / description
      Previous value: -"For posts: ISO 8601 timestamp - only return posts after this time."New value: +"posts (optional): ISO 8601 timestamp - only return posts after this time."
    • changedInput schema / properties / before_time / description
      Previous value: -"For posts: ISO 8601 timestamp - only return posts before this time."New value: +"posts (optional): ISO 8601 timestamp - only return posts before this time."
    • changedInput schema / properties / end_cursor / description
      Previous value: -"For posts: Pagination cursor for next page of results. For videos, reels: Pagination cursor."New value: +"posts (optional): Pagination cursor for next page of results. videos, reels (optional): Pagination cursor."
    • changedInput schema / properties / exact_followers_count / description
      Previous value: -"For details: When true, performs a deeper scrape to return the exact follower count (e.g. 38,493,217 instead of \"38M\"). Charges 5 credits when true, 1 credit otherwise. Default: false."New value: +"details (optional): When true, performs a deeper scrape to return the exact follower count (e.g. 38,493,217 instead of \"38M\"). Charges 5 credits when true, 1 credit otherwise. Default: false."
    • changedInput schema / properties / limit / description
      Previous value: -"For posts: Maximum number of posts to return. Default: 3. Minimum: 3. Maximum: 9. For videos: Maximum number of videos to return. Default: 6. Minimum: 6. Maximum: 12."New value: +"posts (optional): Maximum number of posts to return. Default: 3. Minimum: 3. Maximum: 9. videos (optional): Maximum number of videos to return. Default: 6. Minimum: 6. Maximum: 12."
    • changedInput schema / properties / link / description
      Previous value: -"For details, posts, videos, reels: Facebook page URL. For id: Facebook page URL (e.g., https://facebook.com/nike)."New value: +"details, posts, reels (required): Facebook page URL. id (required): Facebook page URL (e.g., https://facebook.com/nike). videos (optional): Facebook page URL."
    • changedInput schema / properties / profile_id / description
      Previous value: -"For videos: Facebook profile ID (alternative to link)."New value: +"videos (optional): Facebook profile ID (alternative to link)."
    • changedInput schema / properties / timezone / description
      Previous value: -"For posts: Timezone for timestamps (e.g., UTC, America/New_York)."New value: +"posts (optional): Timezone for timestamps (e.g., UTC, America/New_York)."
  4. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the read-only/non-destructive/open-world safety profile, and the description adds a great deal beyond that: per-action credit pricing (including the 5-credit surcharge for exact_followers_count and ceil(posts_returned/3) for posts), per-action return volumes (3-9 posts, 6-12 videos, 8-16 albums), and pagination via end_cursor. The deeper-scrape behavior behind exact_followers_count ('38,493,217 instead of "38M"') is disclosed before the agent spends the credits.

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-loaded summary sentence followed by one consistently formatted block per action, which is the right structure for a 7-action tool. It is dense with no filler, though the repeated 'Pricing: N credit per call' lines and a few Inputs lines restate what the schema already lists, adding mild redundancy.

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?

For a 10-parameter, 7-action tool with an output schema, this definition covers everything an agent needs to choose an action, satisfy its parameter requirements, chain calls (id -> albums -> album_items), and anticipate cost and pagination. Return values are described as a bonus even though the output schema already carries them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, so the baseline is 3, but the description adds workflow semantics the schema cannot express: which parameters each action needs, that profile_id is the numeric ID obtained from action=id, that album_id must come from action=albums or facebook_group, and that link/profile_id are interchangeable for videos. It also explains the effect of after_time/before_time and timezone on the posts action.

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?

The opening sentence names the resource (Facebook pages) and the data surface (profile details, page ID, posts, videos, reels, photo albums), then enumerates all seven actions with a specific verb+object for each. Sibling boundaries are made explicit: facebook_search (action=pages) to find a page by name, facebook_group (action=albums) as another album_id source, and action=videos vs action=reels vs action=posts.

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

Usage Guidelines5/5

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

Every action carries a when-to-use clause plus a named alternative: 'use it when you have the page URL; to find a page by name, use facebook_search (action=pages) first', 'use action=details for the page's data', 'For reels or videos only, use action=reels or action=videos', 'For long-form videos, use action=videos'. Cross-action dependencies (album_id comes from action=albums, profile_id from action=id) are spelled out rather than left to inference.

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

All SocialAPIs toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources