Skip to main content
Glama
Sign In

ReachSocial - One API for social media data.

by dev.reachsocial
OverviewDiscussionsAdmin

X Public Posts

x_feed
Idempotent

Retrieve a provider-selected set of normalized public posts from an X profile. Use for a bounded list from one account/channel. For one specific post/video URL, use x_post. Returns a bounded normalized X feed and temporary media references. Provider ordering is not guaranteed to be chronological. 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

NameRequiredDescriptionDefault
urlYesCanonical X profile URL. Supply a full https:// URL, not a handle or search query.
max_itemsNoMaximum posts to return.
idempotency_keyYesThe 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

NameRequiredDescriptionDefault
dataNoDirect B2B normalized profile, item, or items; feeds may include next_cursor and has_more.
metaNoDirect B2B schema/normalization versions, response shape, and latency.
cachedNoWhether a direct B2B response reused cached normalized data.
resultNoStored execution response after OAuth payment; contains normalized data or a terminal failure.
statusYesB2B success or the current OAuth payment/execution state.
messageNoAction or recovery guidance for the current request state.
serviceYesCatalog service ID, such as instagram.profile.
request_idYesStored request identifier; preserve it for recovery.
payment_urlNoOwner browser link for USDC payment approval; present when payment is required.
price_centsNoOAuth request price in USD cents.
transactionNoSettled payment transaction identifier, when available.
payment_statusNoStored settlement state; uncertainty requires retrieval, never a new payment.
payment_endpointNoOwner-only acceptance endpoint, present only during an explicitly enabled validation run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. Changed14 schema fields changed
    • 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
    • changedInput schema / properties / max_items / default
      Previous value: -20New value: +12
    • addedInput schema / properties / max_items / description
      Added value: +"Maximum posts to return."
    • addedInput schema / properties / max_items / maximum
      Added value: +30
    • addedInput schema / properties / max_items / minimum
      Added value: +1
    • addedInput schema / properties / url / description
      Added value: +"Canonical X 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: -"x_feedDictOutput"New value: +"MCPServiceResult"
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint, idempotentHint, and destructiveHint=false, but the description adds real behavioral context: non-chronological provider ordering, immediate B2B billing, OAuth's $0.05 USDC request on Base with browser approval wait, and an error taxonomy. This explains the otherwise surprising readOnlyHint=false (payment/billing side effect) rather than contradicting it.

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 purpose and sibling routing come first, followed by return behavior, ordering caveat, and payment flow. It is dense but nearly every sentence carries operational information; slight length is justified by the dual B2B/OAuth execution paths.

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?

Annotations, a 100%-covered schema, and an output schema mean the description needn't restate parameters or returns. It nonetheless covers ordering nondeterminism, billing/payment side effects, idempotency retry rules, and error cases, leaving no major gap for a tool with payment gating.

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 fully documents url, max_items, and idempotency_key. The description reinforces retry semantics and new-key-on-changed-input behavior, but adds little on URL format or max_items beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Retrieve ... normalized public posts from an X profile') with scope ('bounded list from one account/channel'). It explicitly distinguishes itself from the sibling x_post for single-post URLs, so an agent can choose 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 Guidelines5/5

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

Gives an explicit when-to-use ('bounded list from one account/channel') and a named alternative for the other case ('For one specific post/video URL, use x_post'). It also documents the follow-up step (get_reachsocial_request) for OAuth payment, which is essential routing detail.

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. toolsInspect
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