Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_albums_list

Read-onlyIdempotent

Retrieve a Facebook Page's photo albums with names, counts, and links. Use it to inventory a Page's albums via the Graph API, with optional paging, limits, and field selection.

Instructions

List a Page's photo albums List a Page's photo albums with names, counts and links. Graph API: GET {page_id}/albums.

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": {
      "page_id": "<page_id>"
    },
    "name": "page_albums_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
fieldsNo
page_idYes
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.
extra_fieldsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the actual endpoint and that albums come back with names, counts and links, which is modest extra context; it says nothing about pagination behavior or token/permission requirements beyond what the schema already documents for access_token.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is repeated word-for-word ('List a Page's photo albums List a Page's photo albums with names, counts and links'), wasting the front-loaded position. What remains after removing the duplicate is a single compressed sentence plus an endpoint.

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

Completeness3/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 not required, and annotations cover the safety profile. However, with six parameters and near-zero schema coverage, the definition leaves pagination and field-selection behavior unexplained, which is a real gap for a paged listing tool.

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

Parameters2/5

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

Schema description coverage is only 17% (effectively just access_token), so the description must compensate, and it does not. Four of six parameters — after, limit, fields, extra_fields — get no explanation of format or effect, and only page_id is implicitly referenced via {page_id}.

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: list a Page's photo albums, including the underlying endpoint GET {page_id}/albums. The 'albums' resource distinguishes it from page_photos_list, though the first sentence is duplicated verbatim, which weakens the framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus page_photos_list, page_get, or other page sub-resource listings, and no prerequisites or exclusions. The Graph API path hints at context but does not tell the agent how to choose between siblings.

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