Example Prompts
A library of prompts you can copy, adapt, and run with any MCP-connected assistant. Each one shows what to ask, what the assistant does behind the scenes, and any caveats.
These assume you’ve already connected Nuelink and have at least one brand and collection set up.
Discovery
Section titled “Discovery”See everything in your account
Section titled “See everything in your account”“Give me an overview of my Nuelink setup: all brands, the collections inside each, and which platforms are connected.”
The assistant chains nuelink_list_brands, then nuelink_list_collections and nuelink_list_channels for each brand, and summarizes the result. Useful for a first session or after a long break.
Find a specific collection
Section titled “Find a specific collection”“Which of my collections post to TikTok?”
The assistant cross-references collections and their default channels, then lists the ones that include TikTok.
Queuing (the recommended default)
Section titled “Queuing (the recommended default)”Plain text post
Section titled “Plain text post”“Add this to the queue for my ‘Weekly Tips’ collection: ‘Tip: batch your content creation. Spend 2 hours once a week shooting and writing, and you’ll never scramble for a post again 🎯’”
One tool call: nuelink_create_post with publishMode: QUEUE. The post slots into the collection’s next available time.
Single image post
Section titled “Single image post”“Queue this image to my Product Launches collection with the caption ‘New season, new scents 🌿 Available Friday.’”
(Paste the image directly into the chat first, or attach it.)
Two tool calls: nuelink_upload_file, then nuelink_create_post with the returned media ID and publishMode: QUEUE.
Carousel (multiple images)
Section titled “Carousel (multiple images)”“Add a carousel post to my Product Launches queue with these 4 images. Caption: ‘Behind the scenes of our autumn shoot… swipe through ➡️’”
The assistant uploads each image, then creates one post with all four media IDs attached. Platforms that support carousels (Instagram, LinkedIn, Facebook) render them as such; others fall back per Platform-Specific Options.
Video post
Section titled “Video post”“Queue this MP4 to my Reels collection. Caption: ‘POV: you finally got around to scheduling your content for the month.’”
Same shape as image, upload first, then create post.
Media via public URLs
Section titled “Media via public URLs”You don’t always need to upload media. If your image or video already lives at a public URL, pass the URL directly and the assistant will use it without going through nuelink_upload_file. This works for:
- Google Drive share links (set to “Anyone with the link can view”)
- Dropbox share links
- OneDrive share links
- Unsplash image URLs
- Any CDN, S3 bucket, or website you control
- Any URL that’s publicly accessible without auth
From a Google Drive link
Section titled “From a Google Drive link”“Queue this Drive link to my Product Launches collection with the caption ‘New season, new scents 🌿’ https://drive.google.com/file/d/1AbCdEf…/view”
The assistant passes the URL into the post’s media array directly. No upload step.
From an Unsplash photo
Section titled “From an Unsplash photo”“Queue a post to my Inspiration collection with this Unsplash image and a quote about creativity: https://images.unsplash.com/photo-1234567”
Same idea, the URL goes straight into media.
Mixing uploaded and linked media
Section titled “Mixing uploaded and linked media”“Queue a carousel to Product Launches: first slide is this image I’m uploading, second slide is this Dropbox link.”
The assistant uploads the first image (gets back a media id), and adds the Dropbox URL as the second media entry. Both end up in the same carousel post.
A few caveats:
- The URL has to actually be public. If a Drive link requires login or a Dropbox link is password-protected, the post will fail, the social platforms can’t fetch it.
- Direct URLs aren’t stored in your Nuelink media library, so you won’t see them in the dashboard’s media tab. Upload if you want them saved for reuse.
- Very large videos hosted elsewhere may time out depending on the source’s bandwidth. For long-form video, uploading is more reliable.
Drafts
Section titled “Drafts”Save without publishing
Section titled “Save without publishing”“Save this as a draft in my Product Launches collection: ‘New launch coming soon… finalizing details, will publish on approval.’”
nuelink_create_post with publishMode: DRAFT. The post is created but doesn’t enter the queue or get scheduled. Review and approve in the Nuelink dashboard.
Iterate, then draft
Section titled “Iterate, then draft”“Draft a caption for a launch announcement of our new candle line: playful, under 200 characters, with one emoji.”
The assistant writes the caption inline. Once you like it:
“Great. Save that as a draft in my Product Launches collection with this image attached.”
This is the safest workflow when you care about every word let the assistant write, you approve, then publish from the dashboard.
Batch drafts for review
Section titled “Batch drafts for review”“I’m going to give you 5 captions. Save each one as a draft in my Daily Tips collection. Caption 1: …”
The assistant makes one nuelink_create_post call per caption with publishMode: DRAFT. You can then review and approve them in the dashboard.
Scheduling (specific dates)
Section titled “Scheduling (specific dates)”Specific date and time
Section titled “Specific date and time”“Schedule this to my Product Launches collection for Friday November 21st at 9:00 AM.”
nuelink_create_post with publishMode: SCHEDULE and the parsed timestamp. The time is interpreted in the brand’s timezone, not your local time. If you want to be explicit, mention it: “9 AM Casablanca time.”
Relative time
Section titled “Relative time”“Schedule this for tomorrow at 8am in my Daily Tips collection.”
The assistant resolves “tomorrow at 8am” to an absolute timestamp using the brand’s timezone. If it’s ambiguous, it’ll ask.
Batch scheduling
Section titled “Batch scheduling”“I’m going to give you 5 captions. Schedule each one to my Daily Tips collection, one per day starting Monday at 10am. Caption 1: …”
The assistant makes one nuelink_create_post call per caption with incrementing scheduled times. Verify the times before approving, relative dates are where mistakes happen.
Publishing immediately
Section titled “Publishing immediately”When you need it live now
Section titled “When you need it live now”“Post this to my Weekly Updates collection right now: ‘Site is back up, sorry for the downtime, full update later today.’”
publishMode: IMMEDIATE. Useful for time-sensitive announcements where queue or schedule isn’t fast enough.
Multi-brand workflows
Section titled “Multi-brand workflows”Same content, two brands
Section titled “Same content, two brands”“Add this announcement to the ‘Company News’ collection in both Fernwood Botanicals and Fernwood Studio queues.”
The assistant resolves both brand IDs, finds the matching collection in each, and creates two separate posts. Captions are identical, there’s no per-platform customization across brands either, the post object is created twice with the same content.
Different caption per brand
Section titled “Different caption per brand”“Queue this image to my Fernwood Botanicals ‘Launches’ collection with the caption ‘Now available 🌿’, and queue it to Fernwood Studio’s ‘Launches’ collection with ‘Now in stores.’”
Two nuelink_create_post calls with different captions, same media uploaded twice (once per brand library, each brand has its own).
Platform-specific touches
Section titled “Platform-specific touches”The alpha supports a limited set of non-content platform options. You cannot customize the caption or first comment per platform; both apply globally to every channel in the collection.
Add a global auto-comment
Section titled “Add a global auto-comment”“Schedule this to my Product Launches collection for Friday at 9am, and add ‘Tap the link in bio to shop 🛒’ as an auto-comment 30 seconds after publishing.”
The auto-comment fires on every channel that supports comments (Instagram, Facebook, LinkedIn, etc.). It’s the same text everywhere.
Tag an Instagram collab
Section titled “Tag an Instagram collab”“Queue this to my Product Launches collection and tag @harperandvine as a collaborator on Instagram.”
The assistant sets platforms.instagram.collab. Other channels in the collection ignore it.
Tag a location
Section titled “Tag a location”“Queue this and add Brooklyn, NY as the location on the Instagram and Facebook posts.”
Set via platforms.instagram.location and platforms.facebook.location.
Post as a Story (Instagram and Facebook only)
Section titled “Post as a Story (Instagram and Facebook only)”“Queue this image as a Story via my Stories collection.”
The assistant sets postAsStory: true. Important: this affects Instagram and Facebook only. If the collection also includes TikTok, X, or others, those channels will publish the same content as a regular feed post.
YouTube tags and playlists
Section titled “YouTube tags and playlists”“Schedule this video to my YouTube collection for Friday at 10am. Tags: skincare, botanicals, spring-collection. Add it to playlist PL123.”
Set via platforms.youtube.tags and platforms.youtube.playlists.
Polls and quizzes are supported on LinkedIn, X, Telegram, Threads, Mastodon, and Bluesky. Other channels in the collection will ignore the poll or fall back to a caption-only post.
Standard poll
Section titled “Standard poll”“Add a poll to my Engagement collection queue: ‘Which scent should we bring back for summer?’ Options: ‘Rosewater & Oak’, ‘Wild Fig’, ‘Jasmine Honey’. Run it for 3 days.”
The assistant builds the poll object (question, options, period: 3d) and creates the post.
Quiz (poll with a correct answer)
Section titled “Quiz (poll with a correct answer)”“Create a quiz poll on my Engagement collection: ‘Which of these is one of our founding ingredients?’ Options: ‘Bergamot’, ‘Rosewater’, ‘Lavender’. The correct answer is option 2. Explanation: ‘Rosewater has been in every formula since day one.’ Run for 24 hours.”
The assistant sets correctOptionIndex: 1 and explanation on the poll object.
Tips for better prompts
Section titled “Tips for better prompts”- Default to “queue” unless you have a reason not to. It respects your scheduling system instead of fighting it.
- Use “draft” when iterating. Saves work without anything going live.
- Name brands and collections explicitly when you have more than one. “Queue this to Launches” is ambiguous; “Queue this to Fernwood Botanicals → Product Launches” isn’t.
- Be specific about timing. “Soon” and “later” aren’t timestamps. “Friday at 9am Casablanca time” is.
- Captions are global, not per-platform. If you want different text on different platforms, post to different collections.
- Don’t paste sensitive content. Your MCP URL contains an API key, don’t share screenshots of it. Customer data, unreleased credentials, and PII shouldn’t be in any prompt.
Got a prompt pattern that’s working well? Send it to support@nuelink.com and we’ll consider adding it here.