# Can Manus research a topic and draft a sourced LinkedIn post?

> Source: https://tareno.co/agents/manus/linkedin
> Language: en
> Last reviewed: 2026-10-24
> Let Manus research approved sources, return a brief with every claim sourced and draft a LinkedIn point of view you review and approve in Tareno.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Manus (manus) |
| Available connection | Custom MCP connection |
| Connection evidence | tested |
| Methods | mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://tareno.co/docs/mcp) |
| Evidence observed | 2026-10-22 |
| Facts reviewed | 2026-10-25 |

Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface.

Agent: Manus · Network: LinkedIn · Hub: [Manus and Tareno](https://tareno.co/agents/manus)

## Short answer

**Can Manus research a topic and turn it into a LinkedIn post with sources?**

Yes, over the tested custom MCP connection to Tareno. Manus reads the sources you approve, compares them, returns a research brief that names the source of every claim and drafts a LinkedIn post from it. It saves the draft through Tareno. Scheduling needs your approval.

Analysts have opinions that depend on evidence, and the evidence takes hours to gather. That is the work Manus is built for: long tasks across many pages that end in one organized result. The weak point of any long autonomous task is trust. Which page did a number come from, and did two sources really agree? This page shows how to ask for a research brief that makes the post checkable, using an energy-market analyst as the example, and how Tareno takes the finished text into a draft that a person reads before anything reaches LinkedIn.

## Example: an energy analyst writes about grid connection queues

Imagine an analyst at an energy consultancy who wants to comment on waiting times for grid connections. She gives Manus six approved sources, the point of view she wants to argue and the audience, project developers. Manus compares the sources, notes that two of them define waiting time differently and returns a brief with seven facts, each with its source and date. She picks four, and Manus drafts a 230-word post that states her view first, uses only those facts and links one source. It confirms her profile with `list_accounts`, saves the text through `create_drafts` and returns the brief next to the draft ID. A colleague reads both in Tareno, and she requests a Monday slot that waits as a pending action.

## Step by step

1. **Use the tested custom connection.** In Manus, add Tareno through the custom MCP option with OAuth and your own account.
2. **Name the sources and the view.** List the sources Manus may use, the sources it must not use and the point of view you want to argue. A research task without a source list produces text you cannot verify.
3. **Ask for the brief before the post.** Request a brief with each fact, its source, its date and any place where sources disagree. Choose the facts that stay, and drop the rest before drafting.
4. **Draft from the chosen facts only.** Ask for a post of about 230 words that states your view first and uses only the chosen facts. Keep the brief next to the draft so a reviewer can verify each line.
5. **Save draft and brief together.** Manus confirms the account with `list_accounts` and saves the post through `create_drafts`. Paste the brief into your review thread, because Tareno stores the post text, not the research behind it.
6. **Request a slot and approve it.** Give a date, a time and an IANA time zone. Tareno holds the request as a pending action until you approve it in the dashboard.

## Prompts to copy

### Research brief

```text
Use only these sources: [URLs]. Compare what they say about [waiting times for grid connections] and return a brief with each fact, its source, its date and any place where two sources define the term differently. Do not write a post yet.
```

### Draft from the chosen facts

```text
Write a LinkedIn post of about 230 words for [project developers] that argues this view: [view]. Use only facts [1, 3, 4 and 6] from the brief, state my view in the first line and link the source of the strongest fact. Mark opinion as opinion.
```

### Verify before saving

```text
Compare the draft with the brief line by line and tell me about any sentence that says more than its source. Rewrite those sentences, and do not save anything to Tareno until I confirm the final text.
```

### Save and hand over

```text
Use Tareno to confirm my LinkedIn account [name] and save the final text as a draft. Return the draft ID next to the brief, so a colleague can check each claim, and do not request a publishing time yet.
```

## LinkedIn in Tareno

- Tareno cannot read LinkedIn posts published outside Tareno or comments on them, so Manus researches the topic outside LinkedIn and does not look at what others posted there.
- LinkedIn offers no transcripts through Tareno, so interviews or talks have to be given to Manus as text.
- Tareno's configuration allows up to 3,000 characters on LinkedIn, and a link gets a preview card, so a 230-word post can carry one source link.
- LinkedIn's documentation says an article post needs its title, description and thumbnail set explicitly, because the API does not scrape the link for a preview.

Official rules ([Microsoft Learn: LinkedIn Posts API](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api), checked 2026-10-24):

- Organic posts can contain text, images, videos, documents, articles, several images or polls. Organic carousels are not supported by the Posts API; they exist only as sponsored content.
- Posting for a company page requires one of the page roles administrator, direct sponsored content poster or content admin. Posting as a member needs the w_member_social permission.
- An article post needs its title, description and thumbnail set explicitly, because the API does not scrape the link for a preview.
- Reading a member's own posts needs r_member_social, a restricted permission that is available to approved users only.

## Mistakes to avoid

- Letting Manus search the open web without a source list. You cannot check what you cannot trace, and weak pages creep in.
- Using a fact whose definition differs between sources. Choose one definition, say which, and keep it consistent in the post.
- Losing the brief. Tareno stores the post, not the research, so keep the brief where reviewers can open it next to the draft.
- Treating a long task as proof of quality. The brief shows where a fact came from; a person decides whether that source is good enough.

## What does not work

- Manus cannot judge whether a source is correct, so facts that carry weight in the post need a check by a person before approval.
- It cannot store its research in Tareno, since Tareno keeps the post draft and not the supporting brief.
- It cannot publish by itself, because scheduling and publishing requests wait for your approval in the Tareno dashboard.

## Frequently asked questions

### Can Manus write a LinkedIn post from its own research?

Yes. Give it approved sources and your point of view, and it returns a brief with a source for every fact and a post that uses only the facts you choose. You verify the facts that matter and approve the request in Tareno.

### How do I connect Tareno in Manus?

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.

### Why ask for a brief before the post?

The brief exposes what the post will rest on. You can drop weak facts and resolve conflicting definitions before any sentence is written, which is cheaper than finding the problem in a polished draft.

### Does Tareno keep Manus' research?

No. Tareno saves the draft text. Keep the research brief in your own review thread so that a reviewer can check each claim against its source before approving the request.

### Can Manus post to LinkedIn on its own?

No. Scheduling and publishing requests become pending actions in Tareno. LinkedIn receives the post only after you approve it in the dashboard, and Manus can only report that it is pending.

### Does Manus need an API key for Tareno?

No. The custom connection uses OAuth, so Manus stores the authorization after you sign in. Do not paste a key or a token into a task or a prompt. After connecting your own Tareno account, run list_accounts and check the returned profiles before creating a draft or requesting a publishing time.

## Tareno tools used

- `list_accounts`
- `create_drafts`

Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them.

## Related

- [Manus × Tareno overview](https://tareno.co/agents/manus)
- [LinkedIn with Tareno](https://tareno.co/channels/linkedin)
- [Repurposing queue](https://tareno.co/features/repurposing-queue)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Remote MCP setup](https://tareno.co/docs/mcp)