Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

facebook_pages_list_tools

Discover every Facebook Pages tool this server exposes, grouped by permission tier and paired with the Graph API endpoint each call uses.

Instructions

List the tools this server exposes List every tool the AI may call, grouped by tier, with the Graph API endpoint behind each. Use this to discover what is available. Graph API: (local).

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

Input Schema

NameRequiredDescriptionDefault
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It implies a read-only, local introspection call ("Graph API: (local)") and describes the tier grouping in the result, but it never explicitly states that nothing is mutated, that no network call is made, or how the local catalog is sourced. For a zero-risk listing tool this is largely acceptable, but the explicit safety statement is missing.

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 purpose is front-loaded, but the first clause duplicates itself ("List the tools this server exposes List every tool the AI may call"), and the trailing "Graph API: (local)." is a leftover fragment with no informational value. Two sentences of real content padded into four fragments.

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?

The tool is simple: one optional parameter, an output schema that defines the returned structure, and a purely informational purpose. The description covers what it does, why to call it, and how results are organized (by tier, with endpoints), so an agent has what it needs; only the explicit read-only/no-side-effect statement is absent.

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

Parameters3/5

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

Schema description coverage is 100% and the single access_token parameter is fully documented in the schema, including its aliases and the fact that it applies only to this call. The description adds nothing about it, which is fine given the schema does the work, so the baseline of 3 applies.

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: it lists the tools the server exposes, grouped by tier, with the Graph API endpoint behind each. That is plainly distinguishable from sibling tools like pages_list or page_posts_list, which operate on Facebook content rather than on the server's own capabilities. It stops short of a 5 only because the opening sentence is restated twice, slightly muddying the headline.

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 to discover what is available" gives an explicit when-to-use trigger: capability discovery before invoking other tools. There is no stated when-not or named alternative, but for an introspection tool the scope is naturally exclusive and no sibling plausibly competes.

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