Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_publish_video

Uploads a local video to a Facebook Page as a Reel or regular video, now or scheduled; confirm public posting first.

Instructions

Upload a local video to the Page, now or scheduled. This is public: confirm first.

as_reel=True uses the Reels API (Meta's Reels specs apply: vertical 9:16, short duration); if the Page cannot post Reels, it falls back to a regular Page video and says so in "note". as_reel=False uploads a regular Page video; files over 50 MB use chunked upload.

:param video_path: Local video path (mp4, mov, ...). :param description: Caption. :param title: Optional title (regular Page videos only; ignored for Reels). :param as_reel: Reel (default) or regular Page video. :param scheduled_publish_time: Optional UNIX seconds, at least 10 minutes ahead. :param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_path": "<video_path>"
    },
    "name": "fb_publish_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
as_reelNo
page_idNo
video_pathYes
descriptionNo
page_access_tokenNo
scheduled_publish_timeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare non-read-only, open-world, non-idempotent, non-destructive; the description adds genuinely new behavior: the post is public and needs confirmation, Reels API constraints (9:16, short duration), automatic fallback to a regular Page video reported in a 'note' field, and chunked upload above 50 MB. These are exactly the non-obvious traits an agent needs before committing a write.

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 with the action and the safety warning, then mode behavior, then a compact param list. The ':param' block restates parameter names but that is warranted given 0% schema coverage; the only mild slack is the parenthetical Reels spec detail.

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 7-parameter public-write tool it covers the decision points (confirm first, Reel vs regular, size threshold, scheduling floor) and even references the 'note' field, which an output schema alone would not contextualize. With annotations handling the safety profile and an output schema present, nothing essential is missing.

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 0%, so the description must carry all seven parameters, and it does: file formats for video_path, caption semantics for description, title being ignored for Reels, as_reel defaulting to Reel, UNIX-seconds scheduling with a 10-minute floor, and page_id defaulting to FB_PAGE_ID. That is meaningful semantics well beyond bare parameter names.

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?

States a specific verb and resource ('Upload a local video to the Page') plus the timing mode ('now or scheduled'), which cleanly separates it from text-post siblings like fb_publish_post. The two-mode split (Reel vs regular Page video) is spelled out immediately, so an agent knows exactly what operation it is invoking.

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?

Gives clear operational conditions: confirm before calling because the result is public, pick as_reel=True vs False for Reels vs regular video, and schedule at least 10 minutes ahead. It stops short of naming sibling alternatives (e.g. reschedule/delete flows) or exclusions, so routing between related publishing tools is left to inference.

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