Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

token_debug

Read-onlyIdempotent

Inspect a Facebook access token to identify its issuing app, granted scopes, owning Page or user, and expiration; omit the token to debug the configured one.

Instructions

Inspect an access token's app, scopes and expiry Debug a Facebook access token: which app issued it, the granted scopes, the Page or user it belongs to, and when it expires. Omit input_token to inspect the token this server is configured with. Graph API: GET debug_token. Needs an app access token to see other apps' tokens; a Page token can debug itself.

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

Input Schema

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive=false, so the safety profile is covered; the description adds the permission model (app token needed for cross-app debugging, self-debugging Page tokens) and the underlying Graph API call (GET debug_token). That auth context is exactly the kind of behavior structured fields cannot express. It does not mention rate limits or failure modes when the token is invalid.

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 outcome, then the detail, then the operational constraints. The opening phrase and the second sentence overlap slightly ("Inspect an access token's app, scopes and expiry" vs "Debug a Facebook access token: which app issued it..."), a small redundancy, but the rest is dense and every clause carries information.

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?

With an output schema present, return-value explanation is not required, and annotations plus the description together cover safety, prerequisites, defaults, and the API surface for a two-parameter tool. The main missing piece is behavior on invalid or expired tokens and how input_token differs in accepted token types.

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%: access_token is documented in the schema (including token/page_token aliases), but input_token has no schema description. The description compensates by explaining that omitting input_token inspects the server's configured token, which is the key semantic for the undocumented parameter. Minor gap: it does not say what input_token accepts (user vs Page vs app token) beyond the general hint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Inspect an access token's app, scopes and expiry") and the second sentence enumerates exactly what is returned: issuing app, granted scopes, owning Page or user, expiry. An agent can distinguish this diagnostic tool from token-management siblings like facebook_pages_set_token or facebook_pages_refresh_token without opening any schema.

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 concrete operating conditions: omit input_token to inspect the server's configured token, and an app access token is required to see other apps' tokens while a Page token can debug itself. These are real prerequisites rather than platitudes. It stops short of explicitly naming an alternative sibling for related token tasks, so it does not reach 5.

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