# Send a weekly digest of new library imports

> List the week's additions and draft a newsletter-style digest — the team reads one email instead of watching six hours.

- For: Team lead
- Category: Team Knowledge & Library Ops
- MCP tools: library_list, run_youtube_tool
- HTML version: https://veridive.com/mcp/use-cases/weekly-import-digest

## The problem

A shared library that grows silently is a shared library that stops mattering: people import things for the team, the team never learns they exist, and six months later the collection is a graveyard of good intentions with a "didn't we have a video about this?" epitaph.

Collections need circulation to stay alive. The weekly digest — here's what got added, here's why it's worth your minutes — is the circulation mechanism, and like most curation rituals it dies of production cost around week four. Unless production costs a prompt.

## How veridive MCP helps

**library_list** pulls the week's additions — sorted newest, tagged by whoever imported them. **run_youtube_tool**'s `summarizer` and `newsletter` turn the list into the digest: what each addition covers, why it earned an import, in a shape people actually read.

The lead's job shrinks to the editorial sentence — which addition matters most this week and for whom — while the mechanics run themselves. The library stays circulated, imports get the audience that justifies them, and "didn't we have a video about this?" gets answered by memory of last Tuesday's digest instead of by re-importing.

## How to run it

1. **Connect veridive MCP** — One-time setup: add the veridive MCP server to Claude, ChatGPT, Cursor or any MCP client and generate your API key. Takes about two minutes.
2. **Pull the week's additions** — Newest imports across the shared library — the digest's raw list.

   ```
   List what was added to my library this week, newest first, with tags.
   ```
3. **Draft the digest** — Per-item blurbs in newsletter shape — what it covers, why it's worth minutes.

   ```
   Draft a short internal digest of these additions: one paragraph each — what it covers and who on the team should care.
   ```
4. **Add the editorial line and ship** — Your one human sentence on top; the rest was mechanics.

   ```
   Tighten the digest to fit one email, lead with the most important addition, and leave a slot for my editor's note.
   ```

## Problems it solves

- Libraries grow silently and die of non-circulation.
- Digest rituals die of production cost by week four.
- Imports without audiences make the import budget look wasteful when it isn't.
- 'Didn't we have a video about this?' — the re-import reflex that funds library entropy.

## Why it's valuable

- Circulation for the cost of two prompts a week — the ritual survives.
- Every import gets its audience; curation effort stops evaporating.
- The digest doubles as a light audit: silent weeks and topic droughts become visible.
- Pairs with the external-beat newsletter workflow if you also curate outward.

## Example prompts

```
This week's library additions, newest first, with tags.
```

```
Digest draft: one paragraph per addition — coverage and audience.
```

```
One-email version, most important first, editor's-note slot.
```

## FAQ

**Does listing the library cost anything?**

No — library_list is free. The summarizer/newsletter drafting steps are metered; a weekly digest over a handful of additions is a trivial spend.

**How is this different from the beat newsletter use case?**

Direction: that one curates the public web outward (your beat's uploads); this circulates your team's own imports inward. Same drafting muscle, different corpus.

**What if some weeks nothing gets imported?**

That's signal — a quiet-week note keeps the ritual alive and gently reminds the team the library exists to be fed. Or skip and let the digest breathe; monthly beats dead.

## Related use cases

- [Curate a newsletter from your beat's best uploads](https://veridive.com/mcp/use-cases/weekly-beat-newsletter.md) — Fresh-upload filters find the week's real signal; the newsletter tool drafts the issue with your framing.
- [Spring-clean a messy shared library](https://veridive.com/mcp/use-cases/library-spring-cleaning.md) — List, filter and search what's actually in there — find the duplicates and the gaps before adding more.
- [Stand up a research library your whole team queries](https://veridive.com/mcp/use-cases/company-research-library.md) — Curate once, query forever: shared imports become a common brain with citations instead of link-dump Slack threads.

---

Part of the veridive MCP use-case library: https://veridive.com/mcp/use-cases.md
Server docs for agents: https://veridive.com/mcp.md