> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/platform-publishing/platforms/facebook.md).

# Facebook API and MCP

Publish to the selected Facebook Page using its pageId, not a personal Facebook profile.

Choose a connected Facebook Page. Publishing to personal Facebook profiles is not supported. Get `pageId` from the account's subaccounts.

## Fields

| Field          | Use                                                                 |
| -------------- | ------------------------------------------------------------------- |
| `pageId`       | Required Facebook Page ID.                                          |
| `mediaType`    | Optional `reel` or `story` for the media format.                    |
| `link`         | Optional URL for a link preview.                                    |
| `firstComment` | Optional first comment after publishing. Stories do not support it. |

For MCP, pass platform-specific fields alongside `accountId`, `platform`, `text`, and `mediaUrls`. For REST, platform-specific target fields belong inside `post.target`. Thread content belongs inside `post.content.additionalPosts`.

## Media and formats

Publish text or image posts to the Page feed. Videos publish as Reels or Stories. A Story requires media. See the Facebook media section for duration and conversion requirements.

Read [Facebook media requirements](/rest-api-reference/publish-post/media.md#facebook) and [upload and conversion rules](/api-and-mcp-concepts/media-uploads-and-conversion.md). Public media URLs go directly in `mediaUrls`. No upload step required.

## MCP example

Call `blotato_create_post` with the following shape. Replace lookup IDs and example media URLs with returned IDs and your media. Adjust the example's settings to the user's request.

```json
{
  "accountId": "ACCOUNT_ID_FROM_LOOKUP",
  "platform": "facebook",
  "text": "A post for your Facebook Page.",
  "mediaUrls": [],
  "pageId": "PAGE_ID_FROM_LOOKUP"
}
```

## REST example

Send this JSON to `POST https://backend.blotato.com/v2/posts` with your `blotato-api-key` header.

```json
{
  "post": {
    "accountId": "ACCOUNT_ID_FROM_LOOKUP",
    "content": {
      "platform": "facebook",
      "text": "A post for your Facebook Page.",
      "mediaUrls": []
    },
    "target": {
      "targetType": "facebook",
      "pageId": "PAGE_ID_FROM_LOOKUP"
    }
  }
}
```

## Verify the result

1. Save the returned `postSubmissionId`.
2. If processing continues, use `blotato_get_post_status` or `GET /v2/posts/:postSubmissionId`.
3. Report the returned status and public URL when supplied.

For scheduling, add `scheduledTime` or `useNextFreeSlot` as an MCP argument or a REST top-level sibling of `post`. See [Scheduling](/api-and-mcp-concepts/scheduling.md) and [completion rules](/api-and-mcp-concepts/async-jobs-and-polling.md).

## Limits and troubleshooting

Select the Page requested by the user when the account has several Pages. A connected personal Facebook account is the authorization account, rather than the posting destination.

See [Facebook account guide](/social-accounts-and-platform-faqs/facebook.md), [platform help](/social-accounts-and-platform-faqs/facebook/faqs.md), and the [Publish Post reference](/rest-api-reference/publish-post.md) for options and examples.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/platform-publishing/platforms/facebook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.