Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_get

Read-onlyIdempotent

Read a Facebook Page's details—such as name, category, contact info, hours, location, picture, verification, follower and like counts—and specify fields to return exactly what you need.

Instructions

Read a Page's fields Read one Page's details: name, category, about, follower and like counts, contact info, opening hours, location, picture, verification status. Pass fields to choose exactly what you need, or extra_fields to add to the defaults. Graph API: GET {page_id}.

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

Input Schema

NameRequiredDescriptionDefault
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

A3.5/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 openWorld, so the safety profile is covered. The description adds the underlying Graph API call (GET {page_id}) and the useful behavioral detail that a default field set exists and extra_fields extends it, but it says nothing about permission requirements, rate limits, or error behavior on invalid page IDs.

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?

Two sentences, front-loaded with the action and the field inventory, followed by the parameter-selection advice. The opening 'Read a Page's fields' slightly restates the following 'Read one Page's details', a small redundancy but nothing wasteful.

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?

An output schema exists, so return values need no explanation, and the access token nuance is handled in the schema. What remains missing for a four-parameter authenticated fetch is the default field set and the accepted page_id format, so it is close to complete but not airtight.

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 description coverage is only 25%, with access_token being the lone documented parameter, so the description must carry fields, extra_fields and page_id. It does clarify the fields-vs-extra_fields distinction (override vs extend defaults), which is real added meaning, but it never specifies page_id format (numeric ID vs username) or what the default field set actually contains.

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 uses a specific verb and resource ('Read one Page's details') and enumerates the returned fields (name, category, about, follower/like counts, contact info, opening hours, location, picture, verification status), which clearly separates it from list-oriented siblings like page_posts_list or pages_list. It stops short of explicitly naming a sibling it is not, so it is clear but not sibling-differentiated to the top level.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-page detail fetch and that fields/extra_fields control payload size. There is no explicit statement of when to prefer this over pages_find or pages_list, and no mention of prerequisites such as required page permissions.

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