Skip to main content
Glama
IvanBBaev

facebook-mcp

by IvanBBaev

Create Reel

facebook_create_reel

Publish a Facebook Reel from a local file as PUBLISHED, DRAFT, or SCHEDULED. Preview with a dry run, then upload in three phases to post to your Page.

Instructions

Publish a Facebook Reel through the three-phase upload (start → transfer → finish) with an explicit video_state: PUBLISHED, DRAFT or SCHEDULED. The file must be local (the protocol streams the bytes from this server). Each publish consumes one of the Page's 30 API Reels per rolling 24 h. Dry run by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
applyNoSet true to actually perform the write. Omitted or false ⇒ the server decides from its configured write mode: usually a dry run that returns a plan preview and changes nothing, but a server (or package) configured apply-first performs the write. To be certain nothing happens, read the result: a dry run always reports the plan and says the write was NOT performed.
titleNoInternal title for the video object.
videoYesLocal file path inside FB_MEDIA_DIR. A remote URL is REFUSED here: the Reels upload protocol has no "fetch this URL" mode, so the bytes must be readable by this server. Meta enforces 9:16 aspect, at least 540x960, 3-90 s, MP4/MOV — none of which is checked locally.
plan_idNoThe `planId` returned by a preceding dry-run preview of this same tool. Required for irreversible and spend-tier writes; plans expire a few minutes after they are created.
profileNoPage profile key (e.g. "brand-a") or a raw Page ID. Omitted ⇒ the default Page (FB_PAGE_ID).
descriptionNoThe Reel caption. Omitted ⇒ the Reel is published without one.
video_stateNoPUBLISHED ⇒ goes live as soon as encoding finishes (there is no unpublish step in this flow). DRAFT ⇒ stays in the Page's draft area. SCHEDULED ⇒ requires scheduled_publish_time, more than 10 minutes and at most 29 days ahead.PUBLISHED
page_timezoneNoIANA timezone name of the Page (e.g. "Europe/Sofia"), used only to echo a scheduled instant in Page-local time next to UTC. Omitted ⇒ the server reads the Page's own timezone; if that read fails the echo is UTC-only.
scheduled_publish_timeNoOnly with video_state:"SCHEDULED". ISO-8601 WITH an explicit offset ("2026-08-01T09:30:00+03:00" / "...Z"); naive local times and raw epoch numbers are refused. Reels accept a shorter window than feed posts: more than 10 minutes and at most 29 days ahead.
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: three-phase upload, dry-run default, local-file-only restriction, per-Page quota of 30 Reels per rolling 24h, and no unpublish step for PUBLISHED. This is exactly the operational nuance an agent needs and goes well beyond readOnlyHint/destructiveHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: purpose first, then constraints and operational details. Every sentence earns its place, and no information is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 params, no output schema), the combination of description and rich parameter documentation covers local-file handling, scheduling, dry-run behavior, and plan flow. However, the description itself does not explicitly state the shape of the result or that a dry run returns a plan_id; the schema implies it through the plan_id parameter, so a small completeness gap remains.

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

Parameters3/5

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

Schema coverage is 100%, and each parameter already carries detailed descriptions. The main description mostly reiterates video_state and the local-file constraint, so it adds little new meaning beyond what the schema provides. Baseline 3 is appropriate because the schema does the semantic heavy lifting.

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 description states a specific verb and resource: 'Publish a Facebook Reel' and distinguishes the operation through the three-phase upload protocol and video_state options. It is clearly distinct from siblings like create_video_post or create_photo_post because it names Reels explicitly and describes the protocol-specific local-file requirement.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: publishing Reels from a local file, with dry-run default and quota implications. It does not explicitly name alternatives or say 'use create_video_post for feed videos', but the Reel-specific wording and upload protocol are sufficient to guide selection among the siblings.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IvanBBaev/facebook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server