Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

facebook_pages_status

Report Facebook Pages server configuration and readiness, including Graph API version, enabled permissions, and live token type, scopes, and expiry; set ping=false to skip the token verification call.

Instructions

Report this server's configuration, readiness, and token expiry Report the configured Graph API version, the enabled tool permissions, and the Facebook token's type, scopes and expiry. The token is checked live with debug_token, so an expired token is reported as expired rather than shown as configured. Set ping=false to skip the live call. Graph API: (local) plus GET /debug_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": "facebook_pages_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
pingNo
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.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavior: the token is checked live via debug_token, so an expired token is reported as expired rather than shown as configured, and ping=false suppresses that live call. It also names the endpoint touched (GET /debug_token). It never states whether the call is read-only or whether it requires a configured token or authentication, which is a meaningful omission for a tool that makes an outbound API call.

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 opening is a run-on that repeats itself ('Report this server's configuration, readiness, and token expiry Report the configured Graph API version...'), with no sentence break between the two clauses. The remaining content is dense and front-loaded, but the duplicated lead-in costs clarity.

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-value explanation is unnecessary, and the description covers the substantive behavior: what is reported, that the token check is live, that expiry is surfaced honestly, and how to skip the live call. The main residual gap is auth/permission requirements and whether the call is safe (read-only), which the absent annotations leave uncovered.

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 coverage is only 50%, and the undocumented parameter is 'ping'; the description compensates by explaining that ping=false skips the live debug_token call, which is exactly the semantics an agent needs. The access_token override is described in the schema itself (including the token/page_token aliases), so the description does not need to repeat it.

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 names a specific verb ('Report') and enumerates exactly what is reported: Graph API version, enabled tool permissions, and the token's type, scopes and expiry. It is clearly distinct from mutation siblings like facebook_pages_refresh_token or facebook_pages_set_token. It stops short of explicitly differentiating itself from token_debug, which overlaps on token inspection, so it lands at 4 rather than 5.

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?

There is one concrete operational guideline: 'Set ping=false to skip the live call', which tells the agent when to change behavior. However, nothing says when to use this status tool versus token_debug, refresh_token or set_token, so alternative routing is left to inference.

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