facebook-mcp

by IvanBBaev

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

API Usage

facebook_usage

Read-onlyIdempotent

Reports recent Graph API rate-limit signals as usage percentages, helping you back off before hitting a throttle.

Instructions

Report the most recent Graph rate-limit signals (X-App-Usage, X-Business-Use-Case-Usage, x-fb-ads-insights-throttle) as usage percentages, so you can back off before hitting a throttle.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`usage`	Yes
`recent`	No
`hasData`	Yes
`throttled`	No
`retryAfterMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.8.0Oct 29, 2026

addedOutput schema / properties / recent

Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "pct": {
+        "type": "number"
+      },
+      "seenAt": {
+        "type": "number"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "seenAt",
+      "value"
+    ],
+    "type": "object"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / retryAfterMs
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / throttled
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / usage / properties / raw / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv0.7.0Aug 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the safe read-only, idempotent, non-destructive profile. The description adds useful behavioral context beyond annotations: it specifies that the tool reports recent Graph rate-limit signals and expresses them as percentages. It does not clarify freshness or sourcing semantics (e.g., whether signals reflect the last API response), which keeps it from a 5.

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 sentence that front-loads the core action and output, then concisely states the operational purpose. Every clause earns its place with no redundant or vague language.

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?

Given the low complexity, zero parameters, annotations covering safety, and an output schema, the description provides enough context to call the tool correctly. It could add a brief note about signal freshness or empty results, but no essential invocation information is missing.

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?

The tool takes zero parameters, so there are no parameter semantics to document. The schema is empty and fully covered, making the baseline of 4 appropriate.

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 states a specific verb and resource: reporting recent Graph rate-limit signals. It names the exact signal headers (X-App-Usage, X-Business-Use-Case-Usage, x-fb-ads-insights-throttle) and the unit (usage percentages). No sibling tool covers rate-limit diagnostics, so an agent can easily distinguish this tool from the content-management siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'so you can back off before hitting a throttle' clearly indicates when to use the tool: proactively checking rate-limit pressure. There are no explicit exclusions or alternatives, but no sibling offers comparable functionality, so the usage context is sufficiently clear.

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

Deploy Server