Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_events_list

Read-onlyIdempotent

List events created by a Facebook Page with start/end times, venue details, and attendee counts to review upcoming or past Page activity.

Instructions

List a Page's events List events created by a Page with start and end times, place and attendee counts. Graph API: GET {page_id}/events.

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_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
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 readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds the Graph API endpoint and the shape of returned records, but says nothing about pagination (after/limit), token requirements, or empty results — areas where a read-only, open-world call needs more context.

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?

The content is brief, but the first two clauses are a run-on with no punctuation ('List a Page's events List events created by a Page...'), repeating the same idea. The endpoint reference is useful; the duplication is not.

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

Completeness2/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, but with seven parameters at 14% coverage and no usage guidance, the description is too thin for a paginated, filterable Graph API listing. It omits filtering and pagination semantics that an agent needs to call it correctly.

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 14%, so the description carries the burden for seven parameters and fails: time, after, limit, fields and extra_fields are never explained. The phrase 'start and end times' describes returned data rather than the `time` filter, which could mislead about how to bound the query.

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 names a specific verb and resource (list a Page's events) and adds what the records contain (start/end times, place, attendee counts), which distinguishes it from siblings like page_posts_list. It stops short of naming which sibling to use for non-event data, but the resource is unambiguous.

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 mention of alternatives such as page_posts_list or page_get for other Page data. The agent must infer usage from the tool name alone.

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