Skip to main content
Glama
Sign In
facebook-mcp

facebook-mcp

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Story

facebook_create_story

Publish a photo or video story to a Facebook Page that stays public for 24 hours. Use dry-run preview first; applying is irreversible and requires a plan ID.

Instructions

Publish a photo or video story on the Page. A story is public at once for 24 hours, cannot be scheduled, and this server cannot delete it, so it is irreversible: applying needs apply:true and the plan_id of a preceding dry run, whatever FB_WRITE_MODE says. Verify with facebook_list_stories. Dry run by default.

Input 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.
mediaYesA photo: an https:// URL Meta fetches itself, or a local file inside FB_MEDIA_DIR. A video: a local .mp4 inside FB_MEDIA_DIR (its bytes are uploaded from this server; a URL is refused).
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).
media_typeYesphoto ⇒ jpeg/bmp/png/gif/tiff, at most 10 MB. video ⇒ a local .mp4.
confirm_tokenNoOut-of-band operator token (FB_CONFIRM_TOKEN) authorizing this one irreversible or spend-tier apply. Needed only when the MCP client cannot show a confirmation prompt. Ask the human operator for it; it is not stored between calls and is never echoed back.
is_ai_generatedNoVideo stories only: label the video as AI-generated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes far beyond the annotations: irreversible (server cannot delete it), not schedulable, 24h public exposure, apply-overrides-FB_WRITE_MODE behavior, plan_id/confirm_token requirements, and dry-run-by-default. These are precisely the risk facts an agent needs before 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.

Conciseness5/5

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

Dense but efficient: the core action, the irreversibility warning, the apply/plan_id prerequisite, and the verification pointer are all front-loaded with no filler sentences.

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 mutation tool with no output schema, it covers the critical concerns: irreversibility, dry-run safety, required apply/plan_id, out-of-band token, and how to verify. Nothing an agent needs to invoke it safely is missing.

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 (apply, plan_id, confirm_token, media_type, etc.) is already richly documented in the schema. The description reinforces the apply+plan_id relationship but adds little syntax/format detail beyond what the schema already carries, so baseline 3 applies.

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 ('Publish a photo or video story on the Page') plus the defining traits (24h public, no scheduling). It is clearly distinguishable from siblings like facebook_create_post and facebook_create_reel by naming 'story' and its one-shot lifetime.

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?

Explains dry-run-by-default, the apply:true + plan_id path to actually publish, and points to facebook_list_stories for verification. It stops short of explicitly contrasting with the reel/photo-post siblings, but the when-to-use and precondition guidance is otherwise strong.

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

Deploy Server

Other Tools