Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

conversation_messages_list

Read-onlyIdempotent

List messages in a Facebook Page conversation, newest first, to review replies and conversation history. Provide a conversation ID to inspect its thread with optional paging and field selection.

Instructions

List messages in a conversation Read the messages of one Page conversation, newest first. Graph API: GET {conversation_id}/messages.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "conversation_messages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
fieldsNo
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
conversation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds two useful behavioral facts beyond them: results are ordered newest-first and the call maps to a specific Graph API path. It says nothing about rate limiting, errors, or how pagination cursors behave.

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?

Two compact sentences with the operation and scope front-loaded and no filler; the only flaw is a missing sentence break between "conversation" and "Read", which slightly blurs the structure.

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?

An output schema exists, so return values need not be described. However, for a paginated list tool with six parameters, the omission of cursor/limit semantics leaves the definition thinner than the tool's complexity warrants.

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 coverage is only 17% — just access_token is documented. The description only implies conversation_id via the endpoint template and never explains after (cursor), limit, fields, or extra_fields, so five of six parameters get no meaning from either structured data or prose.

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 states a specific verb and resource ("List messages") scoped to "one Page conversation" and adds ordering ("newest first") plus the underlying Graph API endpoint. It is clearly distinct from page_conversations_list, though it does not explicitly name sibling tools to contrast with.

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?

Usage is only implied: an agent can infer it needs a conversation_id from a prior conversations listing, but the description never states prerequisites or when to prefer this over other read tools. There are no explicit exclusions or alternatives named.

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