Skip to main content
Glama
Sign In
facebook-mcp

facebook-mcp

by IvanBBaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create label

facebook_create_label

Create a custom Messenger label on a Facebook Page and return its ID for assigning to people; check existing labels first because each call creates a new one.

Instructions

Create a custom Messenger label on the Page (for example "vip" or "refund-pending") and return its id, to put on people with facebook_assign_label. Each call creates a NEW label, so check facebook_list_labels first. Nobody is notified. Dry run by default; apply:true creates it.

Input Schema

NameRequiredDescriptionDefault
nameYesThe label name, 1–64 characters.
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.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.8.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover safety hints, and the description adds substantial context beyond them: duplicates are possible, nobody is notified, the operation is dry-run by default, and apply:true performs the write. This is exactly the behavioral guidance an agent needs before invoking a non-idempotent create tool.

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 short, front-loaded, and every sentence carries operational value: purpose, duplicate warning, sibling routing, notification behavior, and dry-run semantics.

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 create tool with no output schema, the description still states that it returns the label id and covers the key behavioral risks: duplication, dry-run default, and notification side effects. No critical context is missing for correct invocation.

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 description coverage is 100%, so the schema already documents all parameters including name, apply, plan_id, and profile. The description adds useful examples for label names and clarifies apply:true, but does not need to compensate for schema gaps.

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: create a custom Messenger label on the Page, with examples and the returned id. It distinguishes itself from siblings by naming facebook_assign_label for use and facebook_list_labels for checking existing labels.

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?

Explicitly says to check facebook_list_labels first because each call creates a new label, and names facebook_assign_label as the follow-up tool. It also clarifies the default dry-run behavior and how to actually create the label with apply:true.

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