Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

facebook_pages_set_token

Verifies a pasted Facebook access token with debug_token, then applies it to later calls in this session so an expired configured token can be replaced without restarting; scope selects page or user.

Instructions

Use a different Facebook access token for the rest of this session Verify a pasted access token with debug_token, then use it for every later call in this process. Use it when the configured token has expired and a new one has just been minted: no restart is needed. scope 'page' replaces FB_PAGE_TOKEN, scope 'user' replaces FB_USER_TOKEN. The token is not written to the environment, so a restart goes back to the configured value. A token that debug_token rejects is not applied. Graph API: (local) after GET /debug_token.

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": {
      "access_token": "<access_token>"
    },
    "name": "facebook_pages_set_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNopage
access_tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, yet the description discloses the important behavioral facts: the change is process-scoped, is not written to the environment, is lost on restart, and a token rejected by debug_token is never applied. What is missing is concurrency and error-reporting behavior, but the core mutation semantics are well covered.

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?

Front-loaded with the action and then the trigger, with no filler sentences; each clause carries information. The trailing 'Graph API: (local) after GET /debug_token.' is terse to the point of being cryptic and slightly disrupts the flow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool mutates local session state, and the description covers what changes, how long it lasts, what gets overridden, and what fails silently. An output schema exists, so return-value detail is not required, and nothing essential to a correct call is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description must carry the load, and it does: scope 'page' vs 'user' is mapped to FB_PAGE_TOKEN and FB_USER_TOKEN respectively, and access_token is characterized as a pasted token that is validated before application. That adds real meaning beyond a bare string property with a default.

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: swap the Facebook access token for the remainder of the session, and names the validation dependency (debug_token). It distinguishes the behavior from a restart-based token change but never names the sibling facebook_pages_refresh_token, leaving the closest alternative implicit.

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?

Gives a concrete trigger: 'Use it when the configured token has expired and a new one has just been minted,' plus the prerequisite of verifying with debug_token first. It stops short of stating explicit exclusions, such as when to prefer refresh_token instead.

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