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, which platforms are connected, and any automations running.”
The assistant chains nuelink_list_brands, then nuelink_list_collections, nuelink_list_channels, and nuelink_list_automations 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.
Check what’s coming up
Section titled “Check what’s coming up”“What’s scheduled across Fernwood Botanicals for the next week?”
nuelink_list_brand_posts with view: SCHEDULED, sorted by post_date. postDate comes back in UTC, so a careful assistant converts it to the brand’s timezone before listing times. New in 1.3.
See the weekly schedule
Section titled “See the weekly schedule”“When does Fernwood post during the week? Which days have no slots?”
nuelink_get_schedule returns every slot from every collection, grouped by day, in the brand’s timezone. New in 1.3.
Preview before writing anything
Section titled “Preview before writing anything”“Show me the exact brand, collection, channels, caption, and media you’d use for this post. Don’t create it yet.”
No tool call that changes anything. This is the single most useful habit with an assistant that can publish: make it show its work, then confirm. Follow up with “Confirmed, create it as a draft.”
Verify after writing
Section titled “Verify after writing”“List the posts in that collection and confirm mine is a draft with no publish date.”
nuelink_list_posts. Expect status: DRAFT, postingType: DRAFT, postDate: null.
Review drafts before approving
Section titled “Review drafts before approving”“Show me every draft sitting in my Daily Tips collection.”
nuelink_list_posts with status: DRAFT, filtered on the server. Handy when you’ve batch-drafted with an assistant and want to review before publishing from the dashboard.
Audit your media library
Section titled “Audit your media library”“What images are already in Fernwood’s library? I don’t want to upload a duplicate.”
nuelink_list_media with type: IMAGE. New in 1.2.
Setting up structure
Section titled “Setting up structure”New in 1.2. You can now build the containers, not just fill them.
Create a collection
Section titled “Create a collection”“Create a ‘Holiday 2026’ collection in Fernwood Botanicals. Post it to Instagram and LinkedIn, with slots Monday, Wednesday, and Friday at 9am.”
The assistant calls nuelink_list_channels to resolve the Instagram and LinkedIn channel IDs, then nuelink_create_collection with channels and queues: ["Mon 09:00", "Wed 09:00", "Fri 09:00"].
Reuse a collection’s setup
Section titled “Reuse a collection’s setup”“Show me the channels and queue slots on Product Launches, then create a ‘Q4 Campaign’ collection with the same channels and the same slots.”
The assistant reads the source collection’s channels and queues with nuelink_list_collections, then creates the new one with nuelink_create_collection.
Import a blog into a collection
Section titled “Import a blog into a collection”“Inspect fernwood.substack.com and show me the automation settings you’d use for the Newsletter collection. Use loadOldPosts=false and addPostsAsDraft=true. Don’t create it until I confirm.”
Then, after reviewing:
“Confirmed. Create it, then list automations and verify the feed URL, destination collection, and status.”
nuelink_create_automation with type: SUBSTACK, importAsType: IMAGE, and a name for the automation. The two-step matters here more than anywhere else: an automation keeps running after you create it, so a wrong feed or a wrong collection produces posts indefinitely, not once. loadOldPosts: false and addPostsAsDraft: true are the safe first-run settings; switch them once you’ve seen what the feed produces.
Check on a feed
Section titled “Check on a feed”“Is my RSS automation still importing? When did it last run?”
nuelink_list_automations returns lastRun and runCount for each one. A lastRun of 0 means it hasn’t run yet.
Queuing (explicit intent required)
Section titled “Queuing (explicit intent required)”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.
Check the library before uploading
Section titled “Check the library before uploading”“How many images are already in Fernwood’s library? Don’t upload anything.”
nuelink_list_media, read-only. New in 1.2.
Media-list IDs are opaque strings accepted by post creation. An assistant can list the library, resolve the intended asset, and pass that ID unchanged in media[].id. Confirm the asset and destination before creating a post.
Media via direct URLs
Section titled “Media via direct URLs”You can reference media without uploading when the URL is stable and returns the media bytes directly over HTTPS.
A usable URL must:
- Require no login, cookie, or consent page.
- Return image or video bytes rather than an HTML preview page.
- Avoid short-lived authorization parameters.
- Remain accessible when the social platform fetches it later.
Cloud share-page URLs from Google Drive, Dropbox, or OneDrive often redirect to HTML or require temporary authorization and are not reliable direct-media URLs.
From a CDN
Section titled “From a CDN”“Save a draft in my Product Launches collection using this public image URL: https://cdn.example.com/product.jpg.”
The assistant passes the URL in the post’s media array. Test the final resolved URL before using a non-draft mode.
Mixing uploaded and direct media
Section titled “Mixing uploaded and direct media”“Prepare a draft carousel: first slide is the image I attached; second slide is https://cdn.example.com/detail.jpg. Show the target collection and ask before uploading or creating anything.”
The client must be able to read and encode the attached file. The remote MCP server cannot open a local path by itself.
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 them with “show me the drafts in Daily Tips” and approve 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. Scheduled times must be at least 10 minutes in the future.
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.
Changing posts (explicit intent required)
Section titled “Changing posts (explicit intent required)”New in 1.3. The assistant can change when, or whether, a post goes out. It can’t change what the post says: edit the caption or media in the dashboard.
Reschedule
Section titled “Reschedule”“Move the launch post in Product Launches to Friday at 10am.”
The assistant finds the post with nuelink_list_posts, shows it to you, then calls nuelink_update_post with publishMode: SCHEDULE and the new time in the brand’s timezone.
Publish next
Section titled “Publish next”“Make the spring sale post the next one out of the Product Launches queue.”
nuelink_update_post with queuePosition: FRONT. To queue a draft and publish it next, the assistant sends publishMode: QUEUE with queuePosition: FRONT.
Hold a post back
Section titled “Hold a post back”“Take Friday’s announcement out of the schedule and keep it as a draft.”
nuelink_update_post with publishMode: DRAFT. This is the safe way to stop a post, because you can schedule or queue it again later.
Delete a post
Section titled “Delete a post”“Delete the duplicate spring sale post in Product Launches. Show me which post you mean before deleting it.”
nuelink_delete_post, after you’ve confirmed the exact post. Deletion is permanent, and it’s refused unless the account owner has enabled Allow AI to perform sensitive actions in Settings → API. If you only want the post not to go out, ask for a draft instead.
Results
Section titled “Results”New in 1.3. Read what went out to each channel, and how it did.
Check delivery
Section titled “Check delivery”“Did the launch post go out on every channel? Check failed, retrying, and skipped channels too, not only the published ones.”
nuelink_list_published_posts filtered on the post’s ID, once per status. The tool returns only PUBLISHED entries unless it’s asked for others, so without the second sentence an assistant can report success while a channel failed. Each channel gets its own entry, with a status and a link to the post on the platform.
Find failures
Section titled “Find failures”“Did anything fail to publish this week?”
nuelink_list_published_posts with status: FAILED, which lists the channels a post didn’t reach.
Compare performance
Section titled “Compare performance”“What were our five most-liked posts in September?”
nuelink_list_published_posts with publishedFrom and publishedTo around September, sorted by likes. You can also sort by comments or shares.
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).
Set up a new brand’s structure
Section titled “Set up a new brand’s structure”“Fernwood Studio has channels connected but no collections. Create ‘Launches’, ‘Behind the Scenes’, and ‘Customer Stories’, all posting to every connected channel, weekdays at 10am.”
Three nuelink_create_collection calls after one nuelink_list_channels. New in 1.2.
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. Polls take 2 to 4 options, up to 30 characters each.
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. Indexes are zero-based, so option 2 is index 1.
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.
- Ask it to list before it creates. “Show me what’s queued, then add this” catches duplicates before they happen.
- Ask it to preview, then confirm. For anything persistent, make the assistant show the exact target and payload first.
- Ask it to read back. One extra prompt after a write turns “it said it worked” into “I saw that it worked”.
- Prefer a draft to a delete. Moving a post back to
DRAFTstops it from going out, and you can undo it. - Never paste an API key or a compatibility MCP URL into a prompt.
- Captions are global, not per-platform. If you want different text on different platforms, post to different collections.
- Don’t paste sensitive content. 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.