Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

post_insights

Read-onlyIdempotent

Retrieve performance metrics for a single Facebook Page post, including reach, clicks, reactions, and video views, by passing the post ID and the metric names you need.

Instructions

Read one post's metrics Read metrics for a single post: reach, clicks, media views, reactions by type, video views. Pass one or more metric names. Graph API: GET {post_id}/insights.

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>",
      "metrics": "<metrics>"
    },
    "name": "post_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo
metricsYes
post_idYes
breakdownNo
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.1

TDQS

B3.1/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 open-world, so the safety profile is covered. The description adds the concrete Graph API route, which helps an agent reason about the call, but says nothing about rate limits, metric-name validation failures, or permission requirements beyond what the schema's access_token note implies.

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

Conciseness3/5

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

It is short and the endpoint is front-loaded, but the opening phrase "Read one post's metrics" is immediately restated by "Read metrics for a single post", wasting the lead sentence on duplication.

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 exists, so return-value documentation is not owed here, and the metric list is a useful hint. However, for a five-parameter tool with two undocumented optional parameters and only a 20% schema coverage, the description leaves an agent guessing about period and breakdown semantics.

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

Parameters2/5

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

Schema description coverage is only 20%, so the description must carry parameter meaning, and it covers only 'metrics' (one or more names). The 'period' and 'breakdown' parameters are entirely unexplained in both schema and description, and the expected post_id form is not stated.

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?

"Read metrics for a single post" states a specific verb and resource, and the enumerated metrics (reach, clicks, media views, reactions by type, video views) plus the endpoint GET {post_id}/insights make the scope unambiguous. The word "single" implicitly separates it from page-level insights siblings, though no sibling is named.

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?

"Pass one or more metric names" gives the barest invocation guidance. There is no statement of when to choose this over page_insights/page_insights_metrics, nor any note on prerequisites such as which token type or permissions are required.

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