Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

graph_follow

Read-onlyIdempotent

Fetch the next page of a Graph API edge by following the pagination link a previous read returned, carrying the cursor and token so long edges can be paged reliably.

Instructions

Follow a Graph API pagination link Fetch the next page of an edge from the next_url a previous read returned. Graph pagination links already carry the cursor and token, so this is the reliable way to page through a long edge. Graph API: GET .

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": {
      "url": "<url>"
    },
    "name": "graph_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real context beyond them: pagination links are self-contained (cursor and token embedded), making this the reliable paging path, and it states the underlying call shape (GET <absolute url>).

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?

Three short sentences, front-loaded with the action and then the reason. The opening 'Follow a Graph API pagination link' and the following 'Fetch the next page ... from the next_url' restate the same idea, a small redundancy but not harmful.

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 a rich annotation set and an output schema, the description need not explain return values, and it correctly focuses on where the url comes from and why paging this way is reliable. Minor gaps remain: no note on what to do if the link is expired or invalid, and no mention of the token override path.

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 coverage is 50%: access_token is well documented in the schema, but url is only described as 'Url' there. The description compensates by explaining that url is an absolute link taken from a previous read's next_url, which is meaningful beyond the schema. It says nothing about the optional token override, though the schema already handles that.

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?

Specific verb and resource: 'Follow a Graph API pagination link' / 'Fetch the next page of an edge from the next_url a previous read returned.' The 'next page ... previous read returned' framing implicitly separates it from the first-page list tools (page_posts_list, page_photos_list) without naming any of them explicitly.

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?

Clear when-to-use: take the next_url a prior read returned and follow it to page through a long edge, with a rationale ('links already carry the cursor and token'). It does not state the inverse case — use the corresponding list tool for the first page rather than hand-crafting a URL — so it stops short of explicit alternatives.

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