Social Fetch

Get YouTube video transcript

youtube_video_transcript_get

Read-only

Get the transcript for a YouTube video by URL.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Link to the YouTube video whose transcript should be returned.
`link`	No	Alias for `url`. Prefer `url`.
`path`	No	Alias for `url`. Prefer `url`.
`trim`	No	Ignored if this tool does not support it.
`limit`	No	Ignored if this tool does not support it.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`tweetId`	No	Alias for `url`. Prefer `url`.
`language`	No	Optional ISO 639-1 language code (two letters) to prefer when multiple transcripts exist.
`pageSize`	No	Ignored if this tool does not support it.
`tweetUrl`	No	Alias for `url`. Prefer `url`.
`tweet_id`	No	Alias for `url`. Prefer `url`.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`permalink`	No	Alias for `url`. Prefer `url`.
`tweet_url`	No	Alias for `url`. Prefer `url`.
`maxResults`	No	Ignored if this tool does not support it.
`max_results`	No	Ignored if this tool does not support it.
`conversation_id`	No	Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 21, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / link / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / link / type
```
Removed value: -"string"
```

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / path

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `url`. Prefer `url`."
+}

addedInput schema / properties / permalink / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / permalink / type
```
Removed value: -"string"
```

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / tweetId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetId / type
```
Removed value: -"string"
```

addedInput schema / properties / tweetUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweetUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_id / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_id / type
```
Removed value: -"string"
```

addedInput schema / properties / tweet_url / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / tweet_url / type
```
Removed value: -"string"
```

Changed7 schema fields changedSep 12, 2026

addedInput schema / properties / link

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / permalink

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweetId

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweetUrl

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_id

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

addedInput schema / properties / tweet_url

Added value: +{
+  "description": "Alias for `url`. Prefer `url`.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "url"
-]New value: +[
+  "url",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedJul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedJul 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. However, the description adds no additional behavioral context: it does not state what the transcript looks like (plain text, timestamps), whether it can be partial, any rate limits, or authentication requirements. It merely repeats the action already implied by the annotations and title.

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?

The description is a single, short sentence with no redundant words, achieving high conciseness. It is appropriately front-loaded with the action and resource. However, given the tool's simplicity, it might have also included a brief note on the return format without harming conciseness, so it does not earn a perfect 5.

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

Completeness2/5

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

With no output schema and only a one-line description, the tool lacks important context: what the transcript contains, whether it supports language selection (despite a language parameter), and how long the output might be. While the schema and annotations cover safety and parameters, the description fails to explain the output or any caveats, making it incomplete for an agent that needs to know the result shape.

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?

The schema has 100% coverage, so all parameters are already documented. The description adds only the phrase 'by URL', which aligns with the url parameter but is already present in the schema. It does not clarify the purpose of required meta-parameters like context or llm_model, but the schema explains them. Overall, the description adds minimal value beyond the schema, consistent with the baseline of 3 for high coverage.

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 ('Get'), a resource ('transcript'), and the platform ('YouTube video by URL'). This clearly distinguishes it from the many other transcript tools in the sibling list (e.g., reddit_post_transcript_get, tiktok_video_transcript_get). It is not a tautology and leaves no doubt about what the tool does.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or conditions that would select this over other transcript or video tools. The only implied usage is 'for a YouTube video', but there is no explicit contrast with related tools like youtube_video_get or the many other platform-specific transcript tools.

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

All Social Fetch 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.

Get YouTube video transcript

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources