ReachSocial - One API for social media data.

Facebook Profile

facebook_profile

Idempotent

Retrieve normalized public Facebook profile metadata. Use for one account's public profile metadata. Returns normalized public profile fields. Private, gated, and unavailable profiles return an explicit terminal result. An entitled B2B API key executes immediately under the client's billing and spending limits. OAuth requires an approved owner wallet connection and creates a $0.05 USDC payment request on Base; execution waits for browser approval/payment. Then use get_reachsocial_request with the returned request_id. Preserve the idempotency_key for retries; changed input needs a new key. Invalid/private/unavailable targets and access, rate, or spend limits return errors.

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical public Facebook profile URL. Supply a full https:// URL, not a handle or search query.
`idempotency_key`	Yes	The calling agent/client generates this key automatically; do not ask the user to invent it. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it with the exact inputs before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page.

Output Schema

Name	Required	Description
`data`	No	Direct B2B normalized profile, item, or items; feeds may include next_cursor and has_more.
`meta`	No	Direct B2B schema/normalization versions, response shape, and latency.
`cached`	No	Whether a direct B2B response reused cached normalized data.
`result`	No	Stored execution response after OAuth payment; contains normalized data or a terminal failure.
`status`	Yes	B2B success or the current OAuth payment/execution state.
`message`	No	Action or recovery guidance for the current request state.
`service`	Yes	Catalog service ID, such as instagram.profile.
`request_id`	Yes	Stored request identifier; preserve it for recovery.
`payment_url`	No	Owner browser link for USDC payment approval; present when payment is required.
`price_cents`	No	OAuth request price in USD cents.
`transaction`	No	Settled payment transaction identifier, when available.
`payment_status`	No	Stored settlement state; uncertainty requires retrieval, never a new payment.
`payment_endpoint`	No	Owner-only acceptance endpoint, present only during an explicitly enabled validation run.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / idempotency_key / description

Previous value: -"Stable key for this logical request. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."New value: +"The calling agent/client generates this key automatically; do not ask the user to invent it. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it with the exact inputs before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."

Changed10 schema fields changedOct 28, 2026

addedInput schema / properties / idempotency_key / description

Added value: +"Stable key for this logical request. OAuth requires a random 32–255 character key (for example a UUID); B2B accepts 1–255 characters. Save it before calling and reuse it with identical input to recover without duplicate billing. Use a new key for a different target, item limit, or page."

addedInput schema / properties / idempotency_key / maxLength
```
Added value: +255
```
addedInput schema / properties / idempotency_key / minLength
```
Added value: +1
```

addedInput schema / properties / url / description

Added value: +"Canonical public Facebook profile URL. Supply a full https:// URL, not a handle or search query."

addedInput schema / properties / url / format
```
Added value: +"uri"
```
addedInput schema / properties / url / maxLength
```
Added value: +2048
```

addedOutput schema / description

Added value: +"A B2B execution result or an OAuth request awaiting browser payment."

addedOutput schema / properties

Added value: +{
+  "cached": {
+    "description": "Whether a direct B2B response reused cached normalized data.",
+    "title": "Cached",
+    "type": "boolean"
+  },
+  "data": {
+    "additionalProperties": true,
+    "description": "Direct B2B normalized profile, item, or items; feeds may include next_cursor and has_more.",
+    "title": "Data",
+    "type": "object"
+  },
+  "message": {
+    "description": "Action or recovery guidance for the current request state.",
+    "title": "Message",
+    "type": "string"
+  },
+  "meta": {
+    "additionalProperties": true,
+    "description": "Direct B2B schema/normalization versions, response shape, and latency.",
+    "title": "Meta",
+    "type": "object"
+  },
+  "payment_endpoint": {
+    "description": "Owner-only acceptance endpoint, present only during an explicitly enabled validation run.",
+    "title": "Payment Endpoint",
+    "type": "string"
+  },
+  "payment_status": {
+    "description": "Stored settlement state; uncertainty requires retrieval, never a new payment.",
+    "title": "Payment Status",
+    "type": "string"
+  },
+  "payment_url": {
+    "description": "Owner browser link for USDC payment approval; present when payment is required.",
+    "title": "Payment Url",
+    "type": "string"
+  },
+  "price_cents": {
+    "description": "OAuth request price in USD cents.",
+    "title": "Price Cents",
+    "type": "integer"
+  },
+  "request_id": {
+    "description": "Stored request identifier; preserve it for recovery.",
+    "title": "Request Id",
+    "type": "string"
+  },
+  "result": {
+    "additionalProperties": true,
+    "description": "Stored execution response after OAuth payment; contains normalized data or a terminal failure.",
+    "title": "Result",
+    "type": "object"
+  },
+  "service": {
+    "description": "Catalog service ID, such as instagram.profile.",
+    "title": "Service",
+    "type": "string"
+  },
+  "status": {
+    "description": "B2B success or the current OAuth payment/execution state.",
+    "enum": [
+      "success",
+      "payment_required",
+      "awaiting_approval",
+      "reconciliation_required",
+      "succeeded",
+      "failed",
+      "expired"
+    ],
+    "title": "Status",
+    "type": "string"
+  },
+  "transaction": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "Settled payment transaction identifier, when available.",
+    "title": "Transaction"
+  }
+}

addedOutput schema / required

Added value: +[
+  "request_id",
+  "service",
+  "status"
+]

changedOutput schema / title

Previous value: -"facebook_profileDictOutput"New value: +"MCPServiceResult"

First observedOct 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond annotations: discloses the B2B key vs OAuth paths, the $0.05 USDC payment request on Base, browser approval wait, spending/rate limits, terminal-result behavior for private/gated profiles, and idempotency retry semantics. The readOnlyHint=false is consistent with a paid, side-effecting request.

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-loaded with purpose before the payment/flow details, and nearly every sentence carries operational value. The payment paragraph is dense but justified given the multi-step OAuth flow.

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

Completeness5/5

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

With an output schema present, return values needn't be described; the description still covers terminal results, error cases, and the follow-up get_reachsocial_request call. Nothing needed to invoke the tool correctly is missing.

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 schema already documents both url and idempotency_key in detail. The description's 'preserve the idempotency_key for retries; changed input needs a new key' mostly restates the schema rather than adding new syntax or format guidance, so baseline 3 applies.

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?

States a specific verb ('Retrieve'), resource ('public Facebook profile metadata') and scope ('one account's public profile'). Sibling tools are all other platforms/resources, so an agent can route to it without opening schemas.

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?

Gives a clear use condition ('Use for one account's public profile metadata') and routes the OAuth path to get_reachsocial_request with the returned request_id. It doesn't contrast against non-profile Facebook or other-platform profile siblings, but the context and exclusions are otherwise clear.

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

All ReachSocial - One API for social media data. tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?