Meta MCP Server

Set Page Messenger Greeting

meta_set_greeting

Idempotent

Set the greeting text displayed to new Messenger visitors before their first message on a Facebook Page.

Instructions

Sets the Messenger greeting text for a Facebook Page. This is shown to users before they send their first message.

Requires: meta_list_pages called first to load page tokens.

Args:

page_id (string): Facebook Page ID
greeting_text (string): The greeting text (max 160 characters)

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": {
      "page_id": "<page_id>",
      "greeting_text": "<greeting_text>"
    },
    "name": "meta_set_greeting"
  }
}

Input Schema

Name	Required	Description	Default
`page_id`	Yes	Facebook Page ID
`greeting_text`	Yes	Greeting text shown before first message
`response_format`	No	Output format: 'markdown' for human-readable or 'json' for machine-readable	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.2Jun 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish that this is a write, non-destructive, idempotent operation. The description adds useful behavioral context beyond that: where the greeting text appears and the hard dependency on calling meta_list_pages first for page tokens. No contradiction with annotations exists.

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?

The description is compact and well-organized, with the core purpose stated first and the prerequisite called out. The Args section duplicates some schema information, but it is short and does not bloat the description.

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?

For a simple setter with rich schema and annotations, the description covers the essential details: purpose, prerequisite, and the two required parameters. It does not describe return values, but no output schema exists and the response_format parameter helps cover that gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds value by tying page_id to the prerequisite of loading page tokens via meta_list_pages, clarifying where the value should come from. It omits response_format from the Args section, but the schema fully documents that parameter.

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 clearly states a specific action ('Sets the Messenger greeting text') and the exact resource ('Facebook Page'). It also explains when the greeting appears, which differentiates it from sibling tools like meta_set_instant_reply and meta_set_away_message.

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 on when this tool is relevant: the greeting is shown before a user sends their first message. It also provides an explicit prerequisite ('Requires: meta_list_pages called first to load page tokens'), though it does not explicitly name alternative tools or exclusions.

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

Deploy Server