# Can a Paperclip agent draft a manager's monthly retrospective for LinkedIn?

> Source: https://tareno.co/agents/paperclip/linkedin
> Language: en
> Last reviewed: 2026-10-25
> Use a Paperclip retrospective agent with Tareno configured in its runtime to turn a month of run records and budget data into a LinkedIn retrospective that the manager edits and approves.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Paperclip (paperclip) |
| Available connection | Custom MCP connection |
| Connection evidence | documented |
| Methods | mcp |
| Authentication | client_dependent |
| Setup | [Setup guide](https://tareno.co/docs/mcp) |
| Install or connect | [Open setup](https://tareno.co/docs/mcp) |
| Evidence observed | 2026-10-25 |
| 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: Paperclip · Network: LinkedIn · Hub: [Paperclip and Tareno](https://tareno.co/agents/paperclip)

## Short answer

**Can Paperclip help a manager write a monthly LinkedIn retrospective about running agents?**

Yes, once Tareno is configured in the agent's runtime, because Paperclip has no MCP command of its own. A retrospective agent reads the month's run records and budget, drafts what worked, what failed and one change, and saves it through Tareno. The manager decides what to disclose, and a time request stays pending until approved.

Managers who run agents learn things that peers would value: which tasks the agents handled well, where they wasted budget, what a human still had to fix. The learning rarely gets written down. Paperclip keeps the material, with run records, costs and heartbeats, and a retrospective agent can turn a month of it into a first draft in the manager's voice. Paperclip does not add MCP servers itself, so Tareno is configured in the runtime the agent uses, and the draft lands in the manager's account for review. This page follows a head of operations who runs a small company of agents. She decides what the company is willing to say publicly, and she is the only one who can approve a time. Tareno has not tested this end to end.

## Example: a head of operations writes a monthly lessons post

Imagine a head of operations whose agents handle support triage and reporting. At month end her retrospective agent reads the run records and the budget summary and drafts a LinkedIn post: triage runs resolved most tickets without help, a reporting agent overspent on retries, and one change for next month is a cap on retries. She removes a customer's name and a ticket link and rewrites one sentence in her own voice. The agent confirms her profile with `list_accounts` and saves the text with `create_drafts`.

## Step by step

1. **Configure Tareno in the runtime.** Follow the Paperclip overview: add Tareno in the Claude Code adapter's user scope or in Hermes's config, and complete the OAuth flow once as the user that runs the heartbeat. Paperclip itself has no command for this.
2. **Verify the connection.** Check the server from the agent's working directory with the environment the heartbeat uses, then run a read-only `list_accounts`. Your LinkedIn profile in the answer is the check; an empty answer means it has to be connected inside Tareno.
3. **Feed it the month.** Hand the retrospective agent the run records and the budget summary, and tell it to keep observed data apart from inference and to flag any figure missing from the records.
4. **Draw the disclosure line.** Read it as a stranger would. Strip internal ticket links, customer names and figures that nobody approved for publication, then put the closing change into your own words.
5. **File the draft.** The agent checks your profile via `list_accounts` and files the edited text through `create_drafts`, which returns a draft ID. Nothing is scheduled.
6. **Name a time.** Give a day, a time and an IANA zone; `schedule_posts` creates a pending action that you release in the dashboard.

## Prompts to copy

### Check the connection

```text
Use Tareno to list my connected social accounts with platform and account name. Read only: do not create, schedule or publish anything. If you cannot reach Tareno from this run, say so clearly and report which tools you did have available.
```

### Read the month

```text
Read this month's run records and the budget summary for the support and reporting agents. List what the data shows about tasks handled without help, retries and cost, and mark anything you infer. Do not write the retrospective yet.
```

### Write the retrospective

```text
Write a LinkedIn retrospective of about 220 words in the first person for the head of operations: what worked, what failed and one change for next month. Leave out ticket links, customer names and any figure marked as not approved, and list the records each claim rests on.
```

### Save the draft

```text
Use Tareno to confirm my LinkedIn profile [name] and save the approved retrospective as one draft. Return the draft ID and the text, and request no time until I give you the day and the time zone.
```

### Request the slot

```text
Take the draft [draft ID] and ask Tareno to schedule it for [last Friday of the month, 16:00] in [Europe/London]. Return the action ID and remind me that the request still waits for my approval in the Tareno dashboard.
```

## LinkedIn in Tareno

- Lessons, figures and one change fit within the 3,000 characters that Tareno's configuration allows for LinkedIn, so nothing needs trimming.
- Posting for a page requires the connecting member to hold a role that LinkedIn recognises, such as administrator.
- Last month's retrospective cannot be compared with this one, because LinkedIn posts made outside Tareno are unreadable to it.
- A personal profile suits a first-person retrospective, so check which account the draft is saved for.

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

- Quoting cost figures that finance never approved. Flag them and ask before the draft is saved.
- Carrying a customer name over from a support run. Names inside ticket text must be removed by hand.
- Accepting conclusions the data does not back. Keep every inference labelled as such.
- Signing in as the wrong operating-system user, which leaves the heartbeat without credentials.

## What does not work

- Paperclip cannot add an MCP server by itself, because its documentation says the runtime it launches is what speaks MCP.
- The retrospective agent cannot decide what the company may disclose, so the manager removes anything private.
- It cannot publish by itself; a dashboard approval releases every time request.

## Frequently asked questions

### Whose voice should the finished post carry?

The manager's. The agent assembles facts and a first draft, but the opinion and the closing change should be rewritten in your own words before approval.

### Which records does the agent see?

Whatever Paperclip exposes through its runtime: run records, issue history and budget summaries. Limit it to what it needs, since a draft built from tickets may carry customer details.

### Can a heartbeat trigger the retrospective monthly?

Yes. Keep the standing instruction that it only drafts, because Tareno holds every time request as a pending action that you approve in the dashboard.

### How do I confirm the heartbeat sees Tareno?

Check the run viewer for the tool list of a real run, then ask for `list_accounts`. The steps come from Paperclip's own guide and Tareno's documented setups, and no one has run the whole chain end to end.

### Should the retrospective go on a page or a profile?

A first-person retrospective fits a personal profile. A page needs a LinkedIn role such as administrator for the connecting member, and it only appears in `list_accounts` once that role exists.

### Can the retrospective publish itself at month end?

No. The agent can only draft, and each time request waits in the Tareno dashboard until you approve it. Afterwards `get_action_status` shows what LinkedIn answered.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `schedule_posts`
- `get_action_status`

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

- [Paperclip × Tareno overview](https://tareno.co/agents/paperclip)
- [LinkedIn with Tareno](https://tareno.co/channels/linkedin)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Post scheduling](https://tareno.co/features/post-scheduling)
- [Remote MCP setup](https://tareno.co/docs/mcp)