Skip to main content
Glama

Get Facebook Page Insights

meta_get_page_insights
Read-only

Retrieve Facebook Page analytics including impressions, engagement, reactions, fans, views, and video metrics. Specify metrics, period, and date range to get time-series data.

Instructions

Gets analytics/insights for a Facebook Page.

Requires: meta_list_pages called first.

Args:

  • page_id (string): Facebook Page ID

  • metrics (string[]): Metrics to retrieve. Full options: Impressions: page_impressions, page_impressions_unique, page_impressions_organic, page_impressions_organic_unique, page_impressions_paid, page_impressions_paid_unique, page_impressions_viral, page_impressions_viral_unique, page_impressions_nonviral, page_impressions_nonviral_unique Post Impressions: page_posts_impressions, page_posts_impressions_unique, page_posts_impressions_organic, page_posts_impressions_organic_unique, page_posts_impressions_paid, page_posts_impressions_paid_unique, page_posts_impressions_viral, page_posts_impressions_viral_unique Engagement: page_engaged_users, page_post_engagements, page_total_actions, page_negative_feedback Reactions: page_actions_post_reactions_total, page_actions_post_reactions_like_total, page_actions_post_reactions_love_total, page_actions_post_reactions_wow_total, page_actions_post_reactions_haha_total, page_actions_post_reactions_sorry_total, page_actions_post_reactions_anger_total Fans: page_fans, page_fan_adds, page_fan_adds_unique, page_fan_adds_by_paid_non_paid_unique, page_fan_removes, page_fan_removes_unique, page_daily_follows, page_daily_follows_unique, page_daily_unfollows_unique Views: page_views_total, page_tab_views_login_top, page_tab_views_login_top_unique, page_tab_views_logout_top Video: page_video_views, page_video_views_unique, page_video_views_paid, page_video_views_organic, page_video_views_autoplayed, page_video_views_click_to_play, page_video_complete_views_30s, page_video_complete_views_30s_unique, page_video_complete_views_30s_paid, page_video_complete_views_30s_organic, page_video_repeat_views, page_video_view_time, page_video_views_10s, page_video_views_10s_unique, page_video_views_10s_paid, page_video_views_10s_organic Content: page_media_view, page_lifetime_engaged_followers_unique

  • period (string): Aggregation period: 'day', 'week', 'days_28', 'month'

  • since (string, optional): Start date YYYY-MM-DD

  • until (string, optional): End date YYYY-MM-DD

Returns: Time-series data for each metric.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes
metricsNoMetric names — see description for full list of 70+ available metrics
periodNoAggregation periodday
sinceNoStart date YYYY-MM-DD
untilNoEnd date YYYY-MM-DD
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: it returns time-series data, and the args section clarifies what data is fetched. No contradiction with annotations.

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?

Well-structured: summary, prerequisite, args with details, return statement. The metric list is long but necessary for completeness. Could be slightly more concise, but justified.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains the return as 'time-series data for each metric.' All essential aspects (prerequisite, parameters, behavior) are covered. Highly complete for a tools of this complexity.

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

Parameters5/5

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

The description adds significant value beyond the input schema, especially for the 'metrics' parameter, which lists 70+ options organized by category. This goes far beyond the schema's default list and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets analytics/insights for a Facebook Page (specific verb+resource). It distinguishes from siblings like meta_get_page (which gets page info) and meta_get_account_insights (for ad accounts), as seen in the sibling list.

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

Usage Guidelines4/5

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

Explicitly states prerequisite: 'Requires: meta_list_pages called first.' This guides the agent on proper use. It does not explicitly mention when not to use, but the context of sibling tools provides implicit differentiation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server