Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_get_page_insights

Read-only

Retrieve Facebook Page analytics and insights for a chosen period, including engagement, follows, views, and video metrics, with optional custom metrics and date range.

Instructions

Page analytics. Default metrics: page_post_engagements, page_daily_follows_unique, page_follows, page_views_total, page_media_view, page_total_media_view_unique, page_video_views. Metrics Meta has retired are listed in metric_errors.

:param period: day, week, days_28, month, lifetime or total_over_range. :param metrics: Optional custom metric names. :param since: Optional start (YYYY-MM-DD or UNIX seconds). :param until: Optional end (YYYY-MM-DD or UNIX seconds). :param page_id: Optional Page id; defaults to FB_PAGE_ID. :param page_access_token: Optional Page token.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fb_get_page_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo
untilNo
periodNoday
metricsNo
page_idNo
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful operational context: default metrics, retired metrics appearing in metric_errors, period choices, and that page_id defaults to FB_PAGE_ID while page_access_token is optional. It does not disclose rate limits, data freshness/latency, or permission scope for Insights.

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?

The definition is compact and mostly front-loaded: purpose first, then default metrics, then parameter notes. The long default-metric list is dense but useful, and the Sphinx-style :param block is structured rather than wasteful.

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 and annotations are present, so the description does not need to explain return values or safety. It covers parameters and defaults adequately, but it lacks selection guidance relative to Page-level vs post-level siblings and omits API caveats like rate limits or data latency.

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

Parameters4/5

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

With 0% schema description coverage across 6 params, the description compensates well by documenting all parameters: period values, custom metrics, date formats for since/until, page_id defaulting to FB_PAGE_ID, and optional page_access_token. It stops short of explaining validity constraints such as metric/period compatibility or maximum date ranges.

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 states the resource and intent clearly with "Page analytics" and then lists default Page-level metrics, so an agent can tell this returns Page Insights data. It does not distinguish itself from nearby siblings such as fb_get_post_insights or fb_get_page_info, leaving some ambiguity about scope.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and it never names or contrasts the relevant alternatives like post-level insights or basic Page info. The only usage-like information is parameter-level, such as period options and metric defaults.

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