ReachSocial - One API for social media data.

YouTube Channel Videos

youtube_feed

Idempotent

Retrieve a bounded normalized list of recent public videos from a YouTube channel. Use for a bounded list from one account/channel. For one specific post/video URL, use youtube_video. Returns recent video metadata and thumbnails. It does not return downloadable YouTube video bytes. 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
`url`	Yes	Canonical YouTube channel URL. Supply a full https:// URL, not a handle or search query.
`max_items`	No	Maximum videos to return.
`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."

Changed14 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
```
changedInput schema / properties / max_items / default
```
Previous value: -20New value: +12
```
addedInput schema / properties / max_items / description
```
Added value: +"Maximum videos 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 YouTube channel 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: -"youtube_feedDictOutput"New value: +"MCPServiceResult"

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses the two auth paths (entitled B2B key billed under client limits vs OAuth requiring an approved owner wallet), the exact $0.05 USDC payment request on Base with browser approval gating execution, and the error surface (invalid/private/unavailable targets, access/rate/spend limits). The readOnlyHint=false is explained by the payment-request side effect rather than left contradictory.

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 and the sibling exclusion before the payment detail, which is the right ordering. There is mild redundancy — 'bounded' appears in the first two sentences and the payment mechanics occupy several lines — but nearly every sentence carries operational information.

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?

For a paid, auth-gated, idempotent fetch with an output schema present, the description covers the auth decision, cost, approval flow, follow-up tool, retry key policy, and failure modes. Nothing an agent needs to call it safely is missing, and return values are correctly left to the output schema.

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 coverage is 100%, so url, max_items and idempotency_key are all fully documented in the schema itself. The description only restates 'bounded' (max_items) and retry/idempotency semantics that the schema already spells out ('Use a new key for a different target, item limit, or page'), adding little beyond the baseline.

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 a bounded normalized list of recent public videos from a YouTube channel') and immediately contrasts with the sibling that handles single items ('For one specific post/video URL, use youtube_video'). The agent can distinguish it from youtube_channel and youtube_video without opening a schema.

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?

Explicitly scopes usage ('Use for a bounded list from one account/channel') and names the alternative for the other case ('For one specific post/video URL, use youtube_video'). It also routes the follow-up step ('Then use get_reachsocial_request with the returned request_id'), so the agent knows both the entry and the continuation.

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?