Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

pages_list

Read-onlyIdempotent

Lists Facebook Pages a user manages and the tasks held on each, helping you find a page_id before performing Page actions.

Instructions

List the Pages the token's person manages List the Facebook Pages the access token's person can perform tasks on, with the tasks (ADVERTISE, MODERATE, CREATE_CONTENT, ANALYZE, ...) they hold on each. Use this first to find a page_id. Graph API: GET me/accounts. Needs a User access token with pages_show_list. Set FB_USER_TOKEN for a dedicated user token, or use a Page token issued through a person.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pages_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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive. The description adds real value beyond them: the underlying Graph endpoint (GET me/accounts), the required permission (pages_show_list), and the task list returned per page. It says nothing about pagination, result volume, or rate limits, which matter for a list endpoint.

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?

The substantive content (endpoint, permission, return shape, ordering hint) is front-loaded and useful, but the first two sentences duplicate the same listing statement. The trailing token-configuration sentence ('Set FB_USER_TOKEN...') is dense and only loosely relevant to a call-time decision.

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?

An output schema exists, so return values need not be described, and the description nonetheless names the per-page task data. Auth requirements and call ordering are covered. The remaining gap is pagination and field-selection guidance for the under-described optional parameters.

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 20% and four of the five parameters (after, limit, fields, extra_fields) are undocumented in both schema and description. The prose explains the token concept but never clarifies that 'after' is a paging cursor or what 'fields'/'extra_fields' are for, so it does not compensate for the coverage gap.

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?

States a specific verb and resource ('List the Facebook Pages...') plus scope ('the access token's person') and what each result carries (ADVERTISE, MODERATE, CREATE_CONTENT, ANALYZE). It also implicitly separates itself from page_get by telling the agent to use it first to find a page_id. The opening two sentences largely restate each other, which muddies an otherwise clear purpose.

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?

'Use this first to find a page_id' gives explicit ordering guidance relative to the other page tools. It also states the required token scope (pages_show_list) and token setup options. It stops short of naming when a different sibling (e.g. pages_find or page_get) would be preferable.

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