Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_videos_list

Read-onlyIdempotent

List videos published by a Facebook Page, including length, permalinks, thumbnails, and publish status. Use it to review or audit a Page's video library with paging and field selection.

Instructions

List a Page's videos List videos published by a Page, with length, permalinks, thumbnail and publish status. Graph API: GET {page_id}/videos.

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_videos_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.9/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is fully covered without the description. The description adds the underlying Graph API call (GET {page_id}/videos) and the returned attribute set, which is useful, but says nothing about pagination behavior, token requirements, or rate limits beyond what the access_token param already states.

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?

It is short and front-loaded, but the opening is a redundant restatement ('List a Page's videos List videos published by a Page'), which wastes the most prominent sentence. The Graph API endpoint at the end is dense but useful.

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 values need not be explained, and the annotations cover the safety profile. However, for a six-parameter tool with 17% schema coverage, the description leaves parameter semantics and pagination behavior unaddressed, so it is only adequate rather than complete.

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% – only access_token is documented – and the description does not compensate. Pagination parameters (after, limit), field selection (fields, extra_fields) and page_id are left unexplained, with at most a faint hint that the fields relate to the enumerated return attributes. The description needed to carry the burden here and does not.

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 gives a specific verb and resource ('List videos published by a Page') and enumerates returned attributes (length, permalinks, thumbnail, publish status), which is enough to distinguish it from page_photos_list or page_posts_list. It does not explicitly name a sibling to differentiate against, which keeps it below a 5.

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?

There is no when-to-use guidance, no prerequisites, and no routing to alternatives such as page_photos_list or post_insights. The agent must infer usage entirely from the tool name and the one-line purpose.

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