> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/platform-publishing/platforms/youtube.md).

# YouTube API and MCP

Build a YouTube video request with title, privacy, and subscriber-notification settings.

Use a connected YouTube account and a video URL. Provide `title`, `privacyStatus`, and `shouldNotifySubscribers`. The example uses an unlisted video.

## Fields

| Field                     | Use                                                                            |
| ------------------------- | ------------------------------------------------------------------------------ |
| `title`                   | Required title, up to 100 characters. Do not include `<` or `>`.               |
| `privacyStatus`           | Required: `private`, `public`, or `unlisted`.                                  |
| `shouldNotifySubscribers` | Required boolean.                                                              |
| `isMadeForKids`           | Optional audience declaration.                                                 |
| `containsSyntheticMedia`  | Optional synthetic-media declaration.                                          |
| `thumbnailUrl`            | Optional public custom-thumbnail URL. Account verification requirements apply. |
| `playlistIds`             | Optional array of up to 5 playlist IDs from subaccounts.                       |

For MCP, pass platform-specific fields alongside `accountId`, `platform`, `text`, and `mediaUrls`. For REST, platform-specific target fields belong inside `post.target`. Thread content belongs inside `post.content.additionalPosts`.

## Media and formats

Use a video URL in `mediaUrls`. The `text` becomes the description. This publish operation does not create channel banners, profile pictures, or YouTube community image posts.

Read [YouTube media requirements](/rest-api-reference/publish-post/media.md#youtube) and [upload and conversion rules](/api-and-mcp-concepts/media-uploads-and-conversion.md). Public media URLs go directly in `mediaUrls`. No upload step required.

## MCP example

Call `blotato_create_post` with the following shape. Replace lookup IDs and example media URLs with returned IDs and your media. Adjust the example's settings to the user's request.

```json
{
  "accountId": "ACCOUNT_ID_FROM_LOOKUP",
  "platform": "youtube",
  "text": "Your video description.",
  "mediaUrls": [
    "https://example.com/video.mp4"
  ],
  "title": "Your video title",
  "privacyStatus": "unlisted",
  "shouldNotifySubscribers": false
}
```

## REST example

Send this JSON to `POST https://backend.blotato.com/v2/posts` with your `blotato-api-key` header.

```json
{
  "post": {
    "accountId": "ACCOUNT_ID_FROM_LOOKUP",
    "content": {
      "platform": "youtube",
      "text": "Your video description.",
      "mediaUrls": [
        "https://example.com/video.mp4"
      ]
    },
    "target": {
      "targetType": "youtube",
      "title": "Your video title",
      "privacyStatus": "unlisted",
      "shouldNotifySubscribers": false
    }
  }
}
```

## Verify the result

1. Save the returned `postSubmissionId`.
2. If processing continues, use `blotato_get_post_status` or `GET /v2/posts/:postSubmissionId`.
3. Report the returned status and public URL when supplied.

For scheduling, add `scheduledTime` or `useNextFreeSlot` as an MCP argument or a REST top-level sibling of `post`. See [Scheduling](/api-and-mcp-concepts/scheduling.md) and [completion rules](/api-and-mcp-concepts/async-jobs-and-polling.md).

## Limits and troubleshooting

For playlist selection, fetch the account's subaccounts. Custom thumbnails require the supported account verification state. A scheduled Blotato post and an unlisted YouTube video are different outcomes.

See [YouTube account guide](/social-accounts-and-platform-faqs/youtube.md), [platform help](/social-accounts-and-platform-faqs/youtube/faqs.md), and the [Publish Post reference](/rest-api-reference/publish-post.md) for options and examples.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/platform-publishing/platforms/youtube.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.