facebook-pages-mcp

get_post_insights

Fetch engagement metrics for a Facebook post: impressions, clicks, reactions, and user activity.

Instructions

Retrieve engagement metrics for a specific post: impressions, engaged users, clicks, reactions by type, and activity by action type.

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": {
      "post_id": "<post_id>"
    },
    "name": "get_post_insights"
  }
}

Input Schema

Name	Required	Description	Default
`metrics`	No	Metrics to retrieve. Defaults to: post_impressions, post_engaged_users, post_clicks, post_reactions_by_type_total, post_activity_by_action_type.
`post_id`	Yes	The Facebook Post ID (format: pageId_postId).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Jul 29, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are present, so the description must fully convey behavioral traits. It only indicates a read operation ('retrieve'), with no mention of side effects, rate limits, authentication needs, or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence efficiently conveys the core purpose and key metrics, with no wasted words.

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?

For a retrieval tool with two parameters and no output schema, the description covers the input and purpose but omits the response structure or pagination details, leaving some ambiguity about return format.

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?

Schema description coverage is 100%, and the description adds value by listing default metrics (e.g., post_impressions, post_engaged_users) and clarifying the post_id format, which goes beyond the schema's bare descriptions.

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 the tool retrieves engagement metrics for a specific post, listing examples like impressions, engaged users, clicks, reactions, and activity. It distinguishes from sibling tools like get_page_insights (page-level) and get_video_insights (video-specific).

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?

The description implies use for post-level metrics but provides no explicit guidance on when not to use or alternatives. The sibling list suggests differentiation, but the description itself lacks direct usage directions.

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

Deploy Server