Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_conversations_list

Read-onlyIdempotent

Retrieve a Facebook Page's Messenger conversations with participant details, last message snippets, and unread counts.

Instructions

List a Page's message conversations List Messenger conversations a Page has with people, with the last snippet, participants and unread count. Needs a token with pages_messaging. Graph API: GET {page_id}/conversations.

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>"
    },
    "name": "page_conversations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
fieldsNo
page_idYes
access_tokenNoOptional Facebook Page access token for this call only. Use it when the token you hold is not the one this server was configured with, or when the configured token has expired. Takes effect for this call and nothing else. Also accepted as token or page_token.
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds the pages_messaging scope requirement and the underlying GET {page_id}/conversations endpoint, which is useful operational context beyond the annotations. With an output schema present, it doesn't need to explain the return shape.

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

Conciseness3/5

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

Two sentences with no filler, but the opening is a run-on: 'List a Page's message conversations List Messenger conversations a Page has with people' restates the same idea twice before getting to the useful details. Front-loading is acceptable, but the duplicated phrasing costs it.

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

Completeness3/5

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

Because an output schema exists, the return fields don't need prose explanation, and the auth scope plus endpoint are provided. What's missing is guidance on the pagination/field parameters that make up most of the input schema, leaving the definition only partially complete for a 6-parameter tool.

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

Parameters2/5

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

Schema description coverage is only 17% — only access_token has inline documentation. The description uses {page_id} in the endpoint notation and mentions the messaging token, but leaves after, limit, fields and extra_fields entirely unexplained in both the schema and the prose. For a 6-parameter tool, this is a substantial gap the description does not compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'List a Page's message conversations,' and clarifies it means Messenger conversations a Page has with people, including last snippet, participants and unread count. That is enough for an agent to distinguish it from conversation_messages_list. It stops short of explicitly naming the sibling that retrieves messages inside a conversation, which keeps it at 4.

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

Usage Guidelines3/5

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

It gives a real prerequisite in 'Needs a token with pages_messaging' and names the underlying Graph API path, which tells the agent the required auth scope. However, it never says when to use this versus conversation_messages_list or page_get, so the routing decision is left implied rather than stated.

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