# Tumblr Email Scraper (`leads-scraper/tumblr-email-scraper`) Actor

Tumblr Email Scraper SD - Tumblr Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Tumblr results by keyword, location and email domain - Tumblr email extractor.

- **URL**: https://apify.com/leads-scraper/tumblr-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Tumblr Email Scraper

### Tumblr Email Scraper

The **Tumblr Email Scraper** is an Apify Actor that collects publicly indexed contact emails from Tumblr blogs. Give it keywords, get back a structured dataset of artists, writers and micro-blogger leads.

Tumblr is still the home of commission artists, fan writers, zine makers, photographers and niche aesthetic blogs. Many of them publish a commissions or business address right in their blog description.

Google indexes those blog pages, and the Tumblr Email Scraper reads the search results and extracts the address. It never logs in, never opens tumblr.com, and never uses Tumblr's API.

If you have ever run `site:tumblr.com "commissions open" "@gmail.com"` by hand, this is that Tumblr email extractor workflow automated, expanded across dozens of phrasings, deduplicated and exported.

For illustration, fandom and independent-creative outreach, Tumblr remains an underused source of contact discovery that most lead-generation tools ignore entirely.

That is precisely the gap the Tumblr Email Scraper fills: a focused crawler for contact discovery rather than a general-purpose Tumblr scraper.

***

### Key Features of the Tumblr Email Scraper

| Feature | What it means in practice |
|---|---|
| Google-powered data collection | Queries use the `site:tumblr.com` operator, fetched through the Apify GOOGLE\_SERP proxy |
| Query expansion | Each keyword x email-domain pair is searched as a base query, a quoted phrase, an `intitle:` query, and one variant per modifier |
| Subdomain-aware profile URLs | Tumblr handles resolve to their canonical `https://{username}.tumblr.com/` blog URL |
| Domain filtering | Only emails on the domains you list are kept |
| Global deduplication | One row per unique address across every query and page |
| Obfuscation handling | Parses `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, zero-width characters and the full-width `＠` |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` does not match inside `@gmail.company` or `@gmail.com.br` |
| Structural parser | Locates each result's `<h3>` and the smallest surrounding block instead of relying on Google's CSS class names |
| Fallback parser | A markup change degrades to "emails without account details" rather than zero results |
| Concurrency control | An `asyncio` worker pool runs queries in parallel with a shared stop signal |
| Retry logic | Up to 3 attempts per page, exponential backoff, fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not treated as empty |
| Blocked-query requeue | Failed queries are retried once more at the end of the run |
| Resumable state | Input-keyed checkpoints in the key-value store, saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Streaming output | Every lead is pushed to the dataset immediately |
| Run summary | Pages fetched, blocked pages, retries and emails per page are logged |

Tumblr blog titles are highly idiosyncratic, so the structural parser matters here. The Tumblr Email Scraper reads the block around the result rather than assuming a fixed title format.

***

### How the Tumblr Email Scraper Works

The Tumblr Email Scraper is a search-engine crawler, not a Tumblr client.

1. **Read input.** Keywords, location, email domains, caps and concurrency.
2. **Build queries.** `site:tumblr.com` plus your keyword, the quoted email domain, and any location phrase.
3. **Fetch search results.** Asynchronous `aiohttp` requests through the Apify GOOGLE\_SERP proxy.
4. **Parse structurally.** Each result block is located from its `<h3>` title outward.
5. **Extract emails.** A domain-filtered regex runs over the block text, with normalisation and the junk filter applied.
6. **Deduplicate and push.** New addresses go into a global set and straight to the Apify dataset.

Base queries run before expanded variants, so the strongest matches land in the dataset first.

Pagination continues per query until the page cap, the email cap, or a run of pages producing nothing new. That stop rule keeps the Tumblr Email Scraper from burning compute on exhausted queries.

***

### What Data Does It Extract?

Each row the Tumblr Email Scraper writes is one email address plus the account context Google printed beside it.

That usually means the blog handle, a display name where the title is name-shaped, the `https://{username}.tumblr.com/` blog URL, and the description snippet the address came from.

Post results are different: the title is a caption rather than a name, so `fullName` is left empty while `accountName` and the snippet still carry context.

Every row also records the keyword that produced it and the exact Google query used, which makes attribution and segmentation straightforward.

This structured-data design is what separates the Tumblr Email Scraper from a raw email list: you always know where a lead came from.

***

### Input Fields

All input to the Tumblr Email Scraper is set in the Apify Console form or passed as JSON via the API.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["artist", "writer"]` | Search terms describing the Tumblr blogs you want |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; leading `@` optional |
| `maxEmails` | integer (1-10000) | `20` | Stop once this many unique emails are collected |
| `countryCode` | string | `""` | Two-letter country code for the search proxy (US, GB, DE...) |
| `expandQueries` | boolean | `true` | Search each keyword x domain pair in several phrasings |
| `queryModifiers` | array | `["email", "contact", "business inquiries", "collab", "booking", "dm"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer (1-50) | `30` | Page cap per query |
| `maxConcurrency` | integer (1-20) | `5` | How many queries run in parallel |

The defaults shipped with the Tumblr Email Scraper are creative-first. `artist` and `writer` reflect where Tumblr's indexed contact information actually concentrates.

***

### Output Schema

Every dataset item from the Tumblr Email Scraper contains all fourteen fields below.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints (blog handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for post captions |
| `username` | URL-safe handle when Tumblr exposes one; otherwise `null` |
| `profileUrl` | Canonical `https://{username}.tumblr.com/` URL when a handle is known; otherwise empty |
| `url` | Direct Tumblr link when exposed, else the profile URL |
| `description` | Blog description or post snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, e.g. `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

Export the Tumblr Email Scraper dataset as JSON, CSV, Excel, XML or HTML, or read it over the Apify API.

The output schema is identical on every run, which makes downstream CRM ingestion predictable.

***

### Example Input and Output

A realistic Tumblr Email Scraper configuration for commissioning illustration work.

#### Input

```json
{
  "keywords": ["commission artist", "illustrator", "fan artist"],
  "location": "",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 200,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["email", "contact", "business inquiries", "collab", "booking"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

#### Output

```json
{
  "network": "Tumblr",
  "keyword": "commission artist",
  "query": "site:tumblr.com commission artist \"@gmail.com\" contact",
  "title": "inkandmothwing - Commissions open",
  "accountName": "inkandmothwing",
  "fullName": "",
  "username": "inkandmothwing",
  "profileUrl": "https://inkandmothwing.tumblr.com/",
  "url": "https://inkandmothwing.tumblr.com/",
  "description": "Digital illustration and character design. Commissions open. Contact: inkandmothwing.art@gmail.com",
  "email": "inkandmothwing.art@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T13:26:47Z"
}
```

***

### How to Use the Tumblr Email Scraper

1. Open the Tumblr Email Scraper on Apify and click **Try for free**.
2. Replace the default keywords with your niche, for example `zine maker`, `photographer`, `webcomic artist`.
3. Set `customDomains` to the providers your audience actually uses.
4. Set `maxEmails` for the list size you need.
5. Optionally set `location` and `countryCode` to bias results toward one market.
6. Run it and export the dataset as CSV, or read it via the Apify API.

**Tip:** Tumblr's vocabulary is its own. `commissions open`, `art blog` and `fic writer` outperform generic marketing terms.

**Tip:** many Tumblr creators cross-post to other galleries. Running the Tumblr Email Scraper next to the [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) catches artists indexed on only one of them.

**Tip:** if blocked pages appear in the Tumblr Email Scraper run log, lower `maxConcurrency` and re-run. Blocked queries are requeued once automatically.

***

### Use Cases

| Use case | How the Tumblr Email Scraper helps |
|---|---|
| Commissioning artwork | Find illustrators and character artists with public commission emails |
| Fandom and IP marketing | Reach fan creators for licensed merchandise or campaign collaborations |
| Publishing and zine outreach | Contact writers, poets and small-press editors |
| Indie game art sourcing | Find pixel artists, concept artists and animators |
| Merch and print partnerships | Reach designers already selling prints and stickers |
| Music and cover-art briefs | Source cover illustrators for releases |
| Community and event outreach | Invite niche bloggers to conventions and online events |
| Creative recruiting | Source freelance illustrators and writers by style keyword |
| CRM enrichment | Attach a contact channel to Tumblr handles you already track |
| Trend research | Map which aesthetic niches are active, with metadata for segmentation |

Agencies often run the Tumblr Email Scraper once per creative discipline, keeping each dataset separate for clean reporting.

***

### Why Use This Tumblr Email Scraper

Tumblr has no contact directory and no way to filter blogs by "has an email in the description". Manual search runs out of road quickly.

Google caps a single query at roughly 300 results. The Tumblr Email Scraper works around that with query expansion across base, quoted, `intitle:` and modifier variants for every keyword and domain pair.

Extraction inside the Tumblr Email Scraper is stricter than a naive regex. Obfuscated addresses are normalised, placeholders such as `yourname@gmail.com` are rejected, and soft-wrapped fragments are collapsed.

Because leads stream into the dataset as they are found, an aborted or migrated run still leaves you with usable data. Resumable state means a restart continues where it stopped.

Creative audiences spread widely. Run this alongside the [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) and the [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) for commercial design portfolios.

For writers specifically, the [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) and the [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) cover the same authors in a longer-form context.

Membership-funded creators are often easiest to reach through the [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper).

***

### Limitations

Read these before your first Tumblr Email Scraper run. They are honest and structural.

- **Publicly indexed emails only.** If an address is not visible in Google's index, the Tumblr Email Scraper cannot find it. There is no login, no API and no private data.
- **Google's result cap.** A single query returns roughly 300 results maximum. Query expansion mitigates this but does not remove it.
- **`possiblyTruncated`.** `true` means Google's snippet ellipsis touched the address. Verify those rows before sending.
- **Apify GOOGLE\_SERP proxy required.** The Tumblr Email Scraper cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are limited to 100 emails per run. Paid plans are uncapped.
- **Handle availability.** `username` and `profileUrl` populate only when Google exposes a handle. Some rows carry `accountName` and `fullName` with an empty `username`/`profileUrl`. That is a Google limitation, not a bug.
- **Variable yield.** Results depend on keywords, domains and location. No volume is guaranteed.

***

### Related Actors

The same engine behind the Tumblr Email Scraper ships for every major network.

| Actor | What it collects |
|---|---|
| [Tumblr Email and Phone Number Scraper](https://apify.com/leads-scraper/tumblr-email-and-phone-number-scraper) | Emails and phone numbers from Tumblr |
| [Tumblr Phone Number Scraper](https://apify.com/leads-scraper/tumblr-phone-number-scraper) | Public phone numbers from Tumblr |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### FAQ

#### What is the Tumblr Email Scraper?

An Apify Actor that collects publicly indexed contact emails from Tumblr-related Google search results and returns them as structured data.

#### Does the Tumblr Email Scraper log into Tumblr or use its API?

No. No login, no cookies, no browser, no API. Everything comes from public Google search results.

#### Where do the emails the Tumblr Email Scraper returns come from?

From indexed titles, snippets and site labels, usually blog descriptions and post text where the blogger published an address themselves.

#### Do I need a proxy to run the Tumblr Email Scraper?

Yes. It requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### Can I filter by email domain?

Yes, via `customDomains`. Matching is boundary-correct, so `@gmail.com` never matches `@gmail.company`.

#### How many emails can one Tumblr Email Scraper run return?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped, bounded by `maxEmails` and by how much Google has indexed.

#### Why is `username` sometimes `null`?

Google does not always print a handle. When it does not, you still get `accountName`, `fullName` and the snippet, but `username` and `profileUrl` stay empty.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the address, so it may be cut off. Verify those rows before adding them to a campaign.

#### Are the emails verified or deliverable?

No. The Tumblr Email Scraper extracts addresses exactly as published. Verify deliverability yourself before a send.

#### Which keywords work best on Tumblr?

Community-native ones. `commissions open`, `art blog`, `fic writer` and `zine` return far more than broad category words.

#### Should I leave query expansion on?

Yes. Google caps a single query at roughly 300 results, and expansion is how the Tumblr Email Scraper reaches past that ceiling.

#### Can I resume an interrupted Tumblr Email Scraper run?

Yes. Progress is checkpointed in the key-value store, keyed by an input hash, and restored on restart or migration.

***

### Leave a review

If the Tumblr Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions, a bug, or need a custom build of the Tumblr Email Scraper? Email **neurodata.apify@gmail.com**.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Tumblr accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Tumblr.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "artist",
    "writer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Tumblr Email Scraper, stored in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "artist",
        "writer"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/tumblr-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "artist",
        "writer",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "email",
        "contact",
        "business inquiries",
        "collab",
        "booking",
        "dm",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/tumblr-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "artist",
    "writer"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "email",
    "contact",
    "business inquiries",
    "collab",
    "booking",
    "dm"
  ]
}' |
apify call leads-scraper/tumblr-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/tumblr-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/tdY7g3eZ6XVitKtVr/builds/oo3OSnpnBr5qT5kvj/openapi.json
