ThumbnailCreator for Muse

Use ThumbnailCreator from Muse to create thumbnails, improve existing images, prepare short video clips, write YouTube metadata, organize creative assets, and publish approved thumbnails to your own channels.

Connection settings

Create a dedicated key in Settings → Developers → API Keys while signed into your ThumbnailCreator account. Store the key in Muse's connector credentials, never in a conversation or example prompt. Revoke it in ThumbnailCreator to disconnect. Each key accesses its organization; YouTube operations additionally require the individual key owner and their personally connected channel.

The connector is submitted through Muse's review program. Submission does not mean it is approved or available in the public directory.

What you can do

Example prompts

• “Analyze this YouTube video and generate four thumbnail concepts using my saved face and brand colors. Show me the credit cost first.”
• “Compare these thumbnails, explain their readability problems, and improve the best one.”
• “Replace the background with a clean studio scene, preserve my face, and make the headline readable on mobile.”
• “Find my latest thumbnails, put the three approved designs in a collection, and generate title options.”
• “Find three highlights in this video and show me the timestamps before rendering vertical clips.”
• “Show my connected channel's videos and preview the thumbnail you recommend. Ask me before publishing it.”
• “Show the thumbnails previously published to this video and restore the one I select.”

Credits and user control

Check /account/credits before paid operations. Generation, paid editing, critique, and optimization generally cost one credit per image; clip renders cost two credits per clip. The individual operation documentation is authoritative. Credit purchases and subscriptions happen on the ThumbnailCreator website; this connector does not process payments.

Ask the user to approve the number of paid outputs. Preview the exact video and image before YouTube publishing or restoration. Confirm deletions. A request to generate images is not permission to publish them.

YouTube access requires connecting a channel in ThumbnailCreator and granting publishing scopes. The API never returns Google access or refresh tokens. Restoration reapplies a saved, previously published ThumbnailCreator image; it cannot recover an original image that was never saved.

Reliable execution

• Responses normally wrap results in data; list endpoints may also return pagination. Follow the schema for each operation.
• Image generation and edits can take up to 300 seconds. Avoid automatic retries after an ambiguous timeout, because they can consume additional credits. Check generation history first.
• Video-thumbnail and clip exports are asynchronous. Save returned job IDs and poll their status. Do not create another job merely because the first is still running.
• YouTube publishing and restoration require a UUID clientRequestId. Reuse it only for retries of the identical operation. PENDING is not success; confirm APPLIED in publication history. A failed publication is not silently retried.
• Variation packs and scans may partly succeed. Inspect each result and report how many images actually completed.
• Respect 429 responses and Retry-After. 402 means more credits are needed. 401 requires reconnecting credentials. Do not repeatedly retry these errors.
• AI thumbnail scores are creative assessments, not measured click-through rates. Publication view snapshots are observational; they do not prove the thumbnail caused a change in performance.

See the connector OpenAPI specification, interactive API reference, authentication guide, privacy policy, and terms of use.