Socify-mcp

youtube_channel/info

Fetch public channel details. GET ?url= for one channel. POST {"urls":[…],"wait_ms":25000} for many URLs in one request (returns data if finished in time, else status=running + batch_id; poll GET ?batch_id=).. Platform=youtube resource=channel/info. Costs 1 credit(s) per request. Requires Authorization: Bearer <api_key>.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_channel/info"
  }
}

Input Schema

Name	Required	Description
`url`	No	Single channel URL (GET). Required unless using POST urls / GET batch_id.
`urls`	No	POST JSON body: array of channel URLs (max 100) in one request.
`wait_ms`	No	POST: max ms to wait for completion before returning (0–60000, default 25000).
`batch_id`	No	GET: poll a multi-URL job started by POST.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / urls / description

Previous value: -"POST JSON body: array of channel URLs (max 50) in one request."New value: +"POST JSON body: array of channel URLs (max 100) in one request."

Changed5 schema fields changedNov 10, 2026

addedInput schema / properties / batch_id

Added value: +{
+  "description": "GET: poll a multi-URL job started by POST.",
+  "type": "string"
+}

changedInput schema / properties / url / description

Previous value: -"Full YouTube channel URL (@handle, /channel/UC…, /c/…, or /user/…)."New value: +"Single channel URL (GET). Required unless using POST urls / GET batch_id."

addedInput schema / properties / urls

Added value: +{
+  "description": "POST JSON body: array of channel URLs (max 50) in one request.",
+  "examples": [
+    "[\"https://www.youtube.com/@mrbeast\"]"
+  ],
+  "type": "string"
+}

addedInput schema / properties / wait_ms

Added value: +{
+  "description": "POST: max ms to wait for completion before returning (0–60000, default 25000).",
+  "examples": [
+    "25000"
+  ],
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "url"
-]
```

Changed4 schema fields changedNov 10, 2026

removedInput schema / properties / id

Removed value: -{
-  "description": "Channel id (UC…). Provide id or username.",
-  "examples": [
-    "UCX6OQ3DkcsbYNE6H8uQQuVA"
-  ],
-  "type": "string"
-}

addedInput schema / properties / url

Added value: +{
+  "description": "Full YouTube channel URL (@handle, /channel/UC…, /c/…, or /user/…).",
+  "examples": [
+    "https://www.youtube.com/@mrbeast"
+  ],
+  "type": "string"
+}

removedInput schema / properties / username

Removed value: -{
-  "description": "Channel handle without @.",
-  "examples": [
-    "MrBeast"
-  ],
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "url"
+]
```

AddedNov 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses the 1-credit cost per request, the Bearer auth requirement, and the async batch behavior including the default 25000 ms wait and polling path. It doesn't describe rate limits, error responses, or what the returned channel details contain, which is the main remaining gap.

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?

Dense and front-loaded: purpose first, then invocation modes, then cost/auth metadata. The only blemish is the doubled period ".." after the polling sentence and the slight redundancy between the description and the schema's mode hints.

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?

For a 4-parameter, no-output-schema tool, the description covers the operational essentials an agent needs: mode selection, wait semantics, polling, auth, and credit cost. What it lacks is any indication of what channel details are returned, which is a modest omission given there is no 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%, and the schema already labels url as "(GET)", urls as a POST JSON array capped at 100, wait_ms as 0–60000 default 25000, and batch_id as a polling handle. The description mostly restates that GET/POST mapping, adding only the running/batch_id outcome, so it sits at the baseline for well-covered schemas.

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?

"Fetch public channel details" gives a specific verb and resource, and the "Platform=youtube resource=channel/info" line reinforces that this is channel-level metadata rather than the videos/shorts/streams sub-resources of the sibling tools. It never explicitly names a sibling, so differentiation is implied by the resource path rather than stated.

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 description clearly routes the agent between invocation modes: GET ?url= for a single channel, POST with a urls array for bulk, and GET ?batch_id= to poll an unfinished job. It also explains the fallback condition (status=running when the wait expires), so the agent knows what to do next. It stops short of saying when to prefer this tool over e.g. bulk channel lookups elsewhere.

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

All Socify-mcp 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?