Manus for Mastodon: Hashtag Research for a Festival
Use Manus with Tareno to study public hashtag timelines on Mastodon, find the tags a festival's audience uses and draft posts that use them, saved for your approval in Tareno.
Can Manus research the hashtags a festival's audience uses on Mastodon and draft posts with them?
Yes, over the tested custom MCP connection. Manus reads public hashtag timelines, finds which tags the festival's audience actually uses, proposes a short list and drafts posts that use them, saved as drafts through Tareno. Every request needs your approval in Tareno.
On Mastodon, hashtags are how people find things, since there is no algorithmic feed to surface a post. A festival that uses the wrong tag is invisible to the audience that would want it, and a festival that stuffs ten tags in is ignored. The right tag is the one the community already uses, and finding it means reading public timelines for an hour. That is a long, dull task that suits Manus. This page follows a small folk festival through hashtag research, with the difference between learning from public posts and copying them, the care needed with accounts and the connection that Manus needs today.
Example: a folk festival looks for its audience's hashtags
Imagine a festival organizer who gives Manus the programme and asks which hashtags the folk-music community uses on Mastodon. Manus reads public timelines for six candidate tags, finds that FolkMusic and FolkFestival are active, that Folk is too broad and that a regional tag is used for local events. It proposes three tags, with how often each appeared in the week it read, and drafts three posts that use them. It saves the drafts with create_drafts for the festival's account, and the organizer checks that none of the posts tags an account she has not verified.
Step by step
01
Connect Tareno as a custom connector
Add the Tareno endpoint as a custom MCP connection with OAuth.
02
Give the programme and candidate tags
List the festival's genre, region and a few candidate hashtags. Manus reads the public timelines for them and reports what it found.
03
Ask for counts and dates
Request how often each tag appeared in the period read, with the date range. A tag active a year ago and quiet now is no use.
04
Choose a short list
Pick two or three tags, not ten. Mastodon readers dislike tag stuffing, and servers may have rules about it.
05
Draft posts with the chosen tags
Ask for posts within your server's limit that use the tags naturally, with hashtags written in capitalized words. Do not tag accounts you have not verified.
06
Save, request and approve
Manus confirms the account with list_accounts and saves the drafts through create_drafts. Give times and an IANA time zone, and approve each request in the Tareno dashboard.
Prompts to copy
Research the tags
For a folk-music festival in [region], read the public Mastodon hashtag timelines for #FolkMusic, #FolkFestival, #Folk and #[RegionalTag]. Report, for each, how many posts you saw in the last 14 days, the dates you read and whether the tag is used for music, events or something else. Do not copy any post.
Recommend a short list
Recommend two or three tags for our posts and explain why in one sentence each, based on the counts you found. Tell me which of the six tags to avoid and why, and tell me how many timelines you could actually read.
Draft the posts
Write three Mastodon posts for Tareno announcing the festival's line-up, tickets and date, each within 450 characters and using the recommended tags written in capitalized words. Tag no accounts, and avoid more than three hashtags per post.
Save the drafts
Use Tareno to confirm the festival's Mastodon account [handle@server] and save the three approved posts as drafts. Return a table with draft ID and topic, and request no times until I give you the schedule.
Mastodon limits and tools in Tareno
Text
up to 500 characters; hashtags and mentions are supported; plain text, no rich formatting
Images
jpg, png, gif, webp, up to 40 MB each, up to 4 per post
Video
mp4, mov, webm, 0 to 10 min, up to 50 MB, one video per post
Links
links can sit inside the text and get a preview card
What Tareno can read
posts published outside Tareno: no; comments: no; transcripts: no; video download: no
As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
What Mastodon itself documents
Character and media limits are set by each server, not by Mastodon itself. The documentation's example server allows 500 characters and 4 attachments, and counts every link as 23 characters.
A scheduled status must lie at least 5 minutes in the future, and a poll cannot be combined with media attachments.
Visibility can be public, unlisted, private (followers only) or direct, and a content warning can be set with spoiler text.
Mastodon is organized by hashtags rather than a ranking algorithm, so the tags a post carries decide who finds it.
Tareno's configuration for Mastodon supports hashtags and mentions inside the 500 characters, but Mastodon's documentation says limits are set per server.
Tareno does not read Mastodon timelines, posts or replies; Manus does the reading itself on public pages and brings the result into the plan.
Mastodon's documentation says a scheduled post must be at least 5 minutes ahead, so a line-up announcement can be queued for the moment tickets open.
What does not work
Manus cannot read private or followers-only posts, so its picture of a community is limited to public timelines.
It cannot tell which accounts want to be tagged, so you decide whom to mention.
It cannot publish a post on its own, since a time request becomes a post only after you approve it in the Tareno dashboard.
Mistakes to avoid
Using a very broad tag. A tag with thousands of daily posts buries yours.
Stuffing posts with tags. Two or three relevant ones read better and respect server norms.
Tagging accounts you have not verified. A wrong tag notifies a stranger.
Assuming a public listing exists. Manus connects to Tareno through a custom connection today.
Open the client's MCP server settings. Add Tareno with the HTTPS endpoint below using Streamable HTTP. This requires support for authenticated remote MCP, not just local stdio servers.
Choose OAuth, connect and sign in with your own Tareno account. Check the requested permissions. Refresh the client's tool list after authorization.
Run list_accounts first. Confirm the returned workspace and account IDs before creating a draft. If no accounts appear, connect a social account in Tareno first.
https://tareno.co/api/mcp
Use the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
Not currently. The tested route is a custom MCP connection that you set up yourself, and a public listing has yet to be approved. Your Manus plan and workspace decide whether the route is open to you.
Why research hashtags at all?
Because on Mastodon they are the main route to discovery. A tag that your audience already follows puts the post in front of them, and a tag nobody uses sends it nowhere.
Does Manus read posts from every server?
Only what is publicly visible to it, and public timelines can differ by server. Manus tells you how many it could read and over which dates, so you can weigh the result.
Should I tag the bands that are playing?
Only with the right handles and, ideally, their agreement. Manus can suggest accounts and show where it found them, but a wrong handle tags a stranger, so you verify each before it is in a draft.
Where does Manus keep my Tareno access?
As an OAuth authorization created when you sign in, not as a key you type. Anything pasted into a task stays in its history, which is why secrets never belong in one.
Will the festival posts go out without my approval?
No. A scheduling request becomes a pending action in Tareno, and Mastodon receives each post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time.