Skip to main content
Glama
facebook-mcp

facebook-mcp

by tannht

fb_get_post_insights

Read-only

Retrieve engagement and performance metrics for a specific Facebook post or video, including reactions, comments, shares, clicks, media and video views, unique viewers, and view time.

Instructions

Stats for one post or video: reactions/comments/shares plus reactions by type, clicks, media views, unique viewers, video views and view time.

:param post_id: Post id ("{page_id}_{post_id}") or video id. :param page_access_token: Optional Page token.

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": "fb_get_post_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
page_access_tokenNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the metric set and post_id format, but does not discuss permissions, rate limits, or behavior when page_access_token is omitted.

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?

Front-loads the metric list and uses compact :param lines with no redundant sentences. It is slightly list-like but efficient and easy to scan.

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 not be explained. The description covers both parameters and the purpose; only explicit usage guidance and auth caveats are missing for this read-only insights call.

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 0%, so the description carries the full burden. It documents post_id format ('{page_id}_{post_id}' or video id) and marks page_access_token as optional, adding meaning beyond the bare schema.

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?

States it returns stats for one post or video and enumerates the metrics, which distinguishes it from page-level insights by scope. It lacks a direct verb like 'retrieve', but the resource and scope are clear.

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?

Implies use for a single post or video but gives no explicit when-to-use, when-not, or alternative such as fb_get_page_insights. The agent must infer the selection criteria.

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