was-fb-mcp

fb_get_insights

Retrieve metrics and insights for Facebook Pages, Posts, or Ad Accounts by specifying object ID and desired metrics.

Instructions

Get metrics and insights for a Facebook Page, Post, or Ad Account.

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": {
      "objectId": "<objectId>",
      "metric": "<metric>"
    },
    "name": "fb_get_insights"
  }
}

Input Schema

Name	Required	Description
`metric`	Yes	Comma-separated list of metrics (e.g. "page_impressions,page_engagements")
`period`	No	Period (day, week, days_28, month, lifetime)
`objectId`	Yes	Page ID, Post ID, or Ad Account ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.5Jul 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, rate limits, or permission requirements. The description only states the function without depth.

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?

Single sentence, 13 words, efficiently conveys the core action. However, it is too brief and could benefit from structure like bullet points or additional clarification.

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

Completeness2/5

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

No output schema, no annotations, and minimal description. The tool has 3 parameters and returns data, but the description does not explain the response format, error handling, or any advanced details.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description does not add substantial meaning beyond the schema; it merely restates the parameter purposes without new context.

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?

Description clearly states the tool retrieves metrics and insights for a Facebook Page, Post, or Ad Account. It specifies the resource types, making its purpose identifiable, though it could be more specific about the types of metrics.

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?

No guidance on when to use this tool versus sibling tools like fb_list_campaigns or fb_get_page_feed. The description does not mention prerequisites or alternatives.

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

Deploy Server