Loading...
×Use Manus with Tareno to collect the week's public news and regulator updates for a trade association, write short sourced Threads posts and save drafts you approve in Tareno.
Yes, over the tested custom MCP connection. Manus reads the public sources you list, picks the week's relevant items, writes a short post for each that names its source and saves drafts for your Threads profile through Tareno. Everything needs your approval in Tareno.
Last reviewed 2026-10-24 · Markdown version for AI agents
Trade associations and professional bodies earn their members' attention by telling them what changed this week, and that means reading the regulator's pages, the trade press and a few mailing lists every Friday. It is real work, the sort that is skipped when things get busy. Manus is built for research that takes many pages, and Threads is a place where a short, sourced item gets read and discussed. This page follows an association for independent pharmacies through a weekly digest, with the sourcing rule that makes it trustworthy, the cap on how many items are worth posting, and the manual connector that Manus needs today.
Imagine an association that gives Manus a list of twelve public sources: the regulator's news page, two trade magazines and a ministry bulletin. On Friday morning Manus reads them, finds nineteen items from the week, and selects the five that affect pharmacies, such as a change in prescription forms. For each it writes a post within 500 characters that states what changed, from when, and names the source. It saves the five drafts with create_drafts for the association's Threads profile. The communications officer checks each against its source, drops one item that only repeats another, and requests the first slot.
Add the Tareno endpoint as a custom MCP connection with OAuth.
List the public pages Manus should read each week. A fixed list makes the digest comparable from week to week and keeps it from drifting toward whatever is loudest.
Request the week's items with their dates and a one-line reason each matters to your members. Items outside the week are dropped.
Ask for five at most. A digest of fifteen posts trains members to ignore it, and Threads is a place for short items.
Request a post per item within 500 characters that states what changed, from when, and names the source. Claims go no further than the source.
Manus confirms the profile 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 after checking its source.
For a Tareno post series, read these sources for items published between [Monday] and [Friday]: [list of URLs]. For each item give the date, the source and a one-line reason it matters to independent pharmacies. Tell me how many sources you could read and which you could not reach.Select the five items that most affect day-to-day pharmacy work and tell me why you left out the rest. If two items cover the same change, keep the one from the primary source and mention the other only as a note to me.Write a Threads post of at most 500 characters for each selected item. State what changed and from when, name the source in the text and avoid advice on what members should do. Mark any item where the source is unclear about the date.Use Tareno to confirm the Threads profile [association handle] and save the five approved posts as drafts, numbered in the order they should appear. Return a table with draft ID and source, and request no times until the communications officer has checked each source.As configured in Tareno on 2026-10-24. The live rules for your own account come from the get_platform_schema tool.
Source: Meta: Threads API, posts, read on 2026-10-24. Platform rules change; check the page before you rely on a number.
https://tareno.co/api/mcpUse the same Tareno account across supported clients. Open the relevant setup guide for authentication, first use, reconnect, and revocation.
list_accountsChecked:
Use the tested custom MCP connection in Manus with OAuth and your own Tareno account. Availability depends on your Manus plan and workspace permissions. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time.
By the reason each matters to your members, using the sources and dates it read. It tells you what it left out, so you can disagree and swap an item before any draft is saved.
It should not. The posts state what changed, from when and from which source. Interpretation in a regulated field belongs to a qualified person, and Manus is told to avoid it.
Manus reports which sources it could not read, and the digest says nothing about them. A missing source is better stated than silently skipped, so the officer can check it by hand.
No. The custom connection uses OAuth with your Tareno account, and Manus stores the authorization. Do not paste a key or token into a task, because it would remain in the conversation.
No. Each scheduling request is a pending action in Tareno, and Threads receives a 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.