Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_list_pages

Read-only

List the Facebook Pages a user manages with IDs, names, categories, followers and tasks, using a user access token with pages_show_list permission.

Instructions

List the Facebook Pages the user manages: id, name, category, followers, tasks.

Needs a USER access token with pages_show_list (FB_USER_ACCESS_TOKEN by default). Page access tokens are never returned; use the get-token CLI to store one.

:param user_access_token: Optional user token; defaults to FB_USER_ACCESS_TOKEN.

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": "fb_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint/openWorldHint), the description discloses the required OAuth scope (pages_show_list), the env-var fallback, and — importantly — that page access tokens are never returned and must be obtained via the get-token CLI. That is real behavioral context an agent needs before chaining calls.

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 prose is front-loaded with what the tool returns, then the auth requirement, which is the right order. The trailing Sphinx-style ':param' line partly repeats the default already stated above, so there is a small amount of redundancy.

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 single optional-parameter read tool with an output schema and readOnly annotations, the auth prerequisite and token caveat are the main gaps an agent could hit, and both are covered. Return values need not be described since an output schema exists, though listing them is harmless.

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 description coverage is 0%, so the description carries the burden; it explains that user_access_token is optional, defaults to FB_USER_ACCESS_TOKEN, and must carry the pages_show_list scope. Only the exact token format is left unstated, which is minor.

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 the user manages') and even enumerates the returned fields (id, name, category, followers, tasks). It does not explicitly distinguish itself from siblings like fb_get_page_info, but the listing scope is unambiguous.

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 implied by the name and the 'pages the user manages' scope, and the auth prerequisite is spelled out. However, there is no explicit when-to-use vs an alternative (e.g., fb_get_page_info for a single page's details) and no exclusions or failure conditions.

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