Subscribr

View saved version →

---
name: subscribr
description: Use when the user wants to research YouTube through Subscribr, organize Subscribr Projects and ideas, read saved scripts, manage Channel templates or writing voice profiles, review assigned work, or create and edit Thumbnail Studio images.
---

# Subscribr Main and Thumbnail Studio

Use the connected Subscribr MCP tools for the user's requested work. The service
is `https://subscribr.ai/mcp/subscribr`. Sign-in happens through the host's OAuth
connection flow. Never ask the user to paste a password, API token, or OAuth code
into the conversation. Do not put credentials in tool arguments or links.

This package includes a remote MCP connection and this workflow skill. It does
not install a CLI executable. The separately installed Subscribr CLI is for
operator-directed local automation; do not use it or REST as a fallback to expand
this plugin's scope. Video Studio rendering, video editing, publishing to YouTube,
saved script text generation/replacement, and billing changes are outside this
integration. You may draft suggestions in the conversation without claiming to
have saved them.

## Find the right workspace and Project

- Use `list_projects` for the Projects board, or `list_my_work` for assigned work
  and notifications. Fetch only the requested data and bounded expansions.
- Use `get_channel_workspace` with `command: overview` or `list_channels` when
  Channel selection is needed. If several Channels match, ask which one.
- Treat returned Team binding, permissions, IDs, revisions, and canonical URLs as
  authoritative. Never substitute another Team or guess an ID. Preserve complete
  typed Project IDs such as `project:v1:script:93`.
- Read a saved script using `get_script_project` with `expand: ["content"]`.
  `create_project` and `promote_idea` create Script-backed Projects, not generated
  script text. `update_project` edits supported metadata and stages only.

See [tool workflows](references/workflows.md) for the catalog and thumbnail commands.
Use the connected tools' actual input schemas for required fields and limits.
Never turn a requested UI feature name into an invented operation.

## Confirm consequential actions

For an archive, promotion, idea generation, or voice commit, request the supported
preview/validation first. Show its effect, target, cost if returned, warnings, and
expiry, then wait for explicit approval before committing. Send the unchanged
bound receipt and normalized data. Use the latest revision and fresh idempotency
key where required. After a timeout, reuse the same key and identical payload;
never change the body under an existing key. On revision conflict, reload and
ask before reapplying. Never assume a preview or a queued job is a completed write.

Before any thumbnail generation or image edit, show the image count and credit
cost and obtain explicit approval. Only then send `confirm: true`. Read the board
again before assigning an image; show which Script-backed Project will receive
it and follow the returned preview/confirmation flow. Do not automatically retry
thumbnail writes after an uncertain result: they are advertised as non-idempotent.
Inspect the board before deciding whether another attempt is needed.

## Thumbnail Studio

1. Resolve the Channel, then call `get_thumbnail_board` to inspect image items,
   statuses, text overlays, and saved people. Thumbnail results are data and
   image links, not an embedded editable canvas in this plugin.
2. Add references with `edit_thumbnail_board` command `add_images`, or propose
   `generate_variations` / `edit_image` with the user's requested visual change.
   Each generated or edited image uses one existing thumbnail credit. Keep
   generation counts small and use the returned schema's limits.
3. Text is a separate editable overlay: use `set_text` instead of baking headlines
   into generated pixels unless the user explicitly requests rendered text.
4. Rendering is asynchronous. Poll `get_thumbnail_board` wi

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.