Skip to main content
Glama
Facebook Pages MCP Server

Facebook Pages MCP Server

by asrrin29

page_insights_metrics

Read-onlyIdempotent

List Facebook Page Insights metric names by purpose, including accepted periods and date presets, plus retired metrics and replacements to avoid failed Insights requests.

Instructions

List Page Insights metric names to try List common Page and post Insights metric names grouped by purpose, plus the periods and date presets the API accepts. Retired metrics are listed separately with their replacements, because one retired metric fails the whole Insights request. Meta changes this list often, so treat it as a starting point and let the API tell you when a metric is unavailable. Graph API: (static reference).

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

Input Schema

NameRequiredDescriptionDefault
groupNo
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.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), so the description only needs added context — and it delivers: it reveals this is a static reference rather than a live call, warns that a single retired metric fails the whole Insights request, and notes the list changes often and may report a metric as unavailable. Minor gap: it does not say whether results are filtered by the optional group argument or what pagination/shape to expect.

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?

The core warning about retired metrics is valuable and front-loaded reasonably, but the opening redundantly restates itself ('List Page Insights metric names to try List common Page and post Insights metric names') and the trailing fragment 'Graph API: (static reference).' is a dangling label that adds noise.

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 no explanation, and the description covers the key domain hazard (retired metrics breaking requests) and volatility of the list. The only real omission is what the `group` argument does, which leaves one of two parameters under-specified.

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 coverage is 50%; access_token is documented in the schema, but the `group` parameter has no description anywhere. The description's phrase 'grouped by purpose' hints at grouping but never states that `group` filters the listing or what values it accepts, so it does not compensate for the coverage gap on the one unexplained parameter.

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 a specific verb and resource — 'List Page Insights metric names' — plus what the listing contains (metrics grouped by purpose, periods, date presets, retired metrics with replacements). It is distinguishable from page_insights/post_insights as a reference/catalog tool rather than a data fetcher, though it never names those siblings explicitly.

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?

Implies usage through 'metric names to try' and 'treat it as a starting point,' which suggests calling this before an Insights request. However there is no explicit when-to-use versus page_insights, no stated prerequisites, and no exclusion guidance — the agent must infer the workflow.

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