# Curate a newsletter from your beat's best uploads

> Fresh-upload filters find the week's real signal; the newsletter tool drafts the issue with your framing.

- For: Curator / Writer
- Category: Content Strategy & Creators
- MCP tools: deep_search, run_youtube_tool
- HTML version: https://veridive.com/mcp/use-cases/weekly-beat-newsletter

## The problem

The curation newsletter is a beautiful product with a brutal cost structure: readers pay attention for your taste, and your taste requires consuming everything to select the five things worth their time. For a video-heavy beat, "everything" is dozens of hours of uploads a week. The math kills most curation newsletters by issue thirty — not for lack of readers, but because the curator burns out on the watching.

The fix isn't lowering the taste bar; it's separating the two jobs curation actually contains. *Coverage* — knowing everything that dropped and what's in it — is mechanical. *Selection and framing* — the part readers subscribe for — is you. One of these jobs should never have been manual.

## How veridive MCP helps

**deep_search** does coverage: this week's uploads across your beat, transcript-read, with quality verdicts pre-filtering the rehash and the sponsor-heavy filler. You review summaries and evidence snippets instead of watching — an hour of reading replaces the week of viewing, and you *still know what's in everything*, which is the credibility a curator can't fake.

**run_youtube_tool**'s `newsletter` and `summarizer` handle the drafting mechanics: structured issue drafts from the videos you selected, in newsletter shape — which you then rewrite with the voice and the take that's the actual product. The treadmill drops from your week; the taste stays.

## 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. **Sweep the week's uploads** — Everything that dropped in your beat this week, quality-filtered — the coverage layer, mechanized.

   ```
   Find this week's uploads about <beat> — substantive content only, no rehash or sponsor-heavy filler — with a one-line summary of what each covers — use veridive's deep_search.
   ```
3. **Select with full information** — You pick the five — but now from summaries of everything, not from whatever you happened to watch.

   ```
   From those, give me more detail on these candidates — key claims and what's genuinely new in each: <video URLs>
   ```
4. **Draft, then make it yours** — The newsletter tool produces the structured draft; your rewrite adds the framing readers subscribe for.

   ```
   Draft a newsletter section for each selected video — what it covers, why it matters this week. I'll add my take on top: <video URLs> — use veridive's run_youtube_tool.
   ```

## Problems it solves

- Curation's coverage cost — watching everything — burns out curators by issue thirty.
- Selection from partial coverage is taste theater: you curate what you happened to see.
- Drafting mechanics (what each video covers) eat the hours that framing deserves.
- Weekly cadence is unforgiving; one busy week breaks the streak that newsletters live on.

## Why it's valuable

- Full-coverage credibility at reading speed — you genuinely know the week, in an hour.
- Quality verdicts pre-filter the noise, so your shortlist starts strong.
- Draft mechanics delegated; your hours go to the take, which is the product.
- The cadence survives busy weeks — the issue ships because the pipeline isn't you watching.

## Example prompts

```
This week's <beat> uploads, substantive only, one-line summaries — use veridive's deep_search.
```

```
Key claims + what's new in these candidates: <URLs>
```

```
Newsletter section drafts per selected video; I'll add the take: <URLs>
```

## FAQ

**Readers subscribe for my taste — doesn't this outsource it?**

It outsources the watching, not the choosing. You select from complete information and write the framing yourself — arguably more your taste than before, when selection was limited to what you'd had time to see.

**How fresh can the sweep run?**

Upload-date filters go down to today; for a weekly issue, a this-week sweep the morning you write is the natural rhythm. Daily briefing formats work too — same pipeline, tighter window.

**Does this work for internal newsletters — a team digest?**

Yes, and it pairs with the library: see the weekly import digest use case for the internal variant built on your team's curated imports.

## Related use cases

- [Send a weekly digest of new library imports](https://veridive.com/mcp/use-cases/weekly-import-digest.md) — List the week's additions and draft a newsletter-style digest — the team reads one email instead of watching six hours.
- [Find the gaps your niche hasn't covered](https://veridive.com/mcp/use-cases/content-gap-finder.md) — Ask what questions keep coming up with weak answers; the uncovered intersection is your content calendar.
- [Monitor a crisis as it unfolds on video](https://veridive.com/mcp/use-cases/crisis-video-monitoring.md) — Fresh-upload sweeps plus comment sentiment show how the story and the reaction are moving hour by hour.

---

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