Naver Blog Post Search & Full Content Extractor: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "제주도 여행"
  ],
  "sortBy": "sim",
  "publishedWithin": "all",
  "categoryNo": 0,
  "maxItems": 3,
  "includeContent": false,
  "includeComments": false,
  "maxComments": 100,
  "includeHtml": false,
  "maxConcurrency": 3
}

---
name: naver-blog-post-search-and-full-content-extractor
description: "Naver Blog posts — titles, authors, blog names, exact publish times, full text, images, tags, categories, and places. Runs the Apify Actor nimbryxo-studio/naver-blog-post-search-and-full-content-extractor. Use when the user needs Naver data with fields such as title, authorName, blogName, publishDate, contentLength, commentCount and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/naver-blog-post-search-and-full-content-extractor"
  store-url: "https://apify.com/nimbryxo-studio/naver-blog-post-search-and-full-content-extractor"
---

# Naver Blog Post Search & Full Content Extractor

Use this skill to fetch Naver data with the Apify Actor `nimbryxo-studio/naver-blog-post-search-and-full-content-extractor` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `blogPosts`, `postDetails`, required | What to fetch. |
| `searchQueries` | array | One or more Korean or English keywords to search across Naver Blog (mode=search). Each query is searched up to Naver's 1,000-result limit. |
| `blogIds` | array | Naver blog IDs or blog URLs (mode=blogPosts). Accepts `hello_world123`, `@hello_world123`, or `https://blog.naver.com/hello_world123`. |
| `postUrls` | array | Naver blog post URLs to fetch in detail (mode=postDetails). Accepts desktop, mobile, PostView, and bare `blogId/logNo` forms. |
| `sortBy` | one of `sim`, `date` | Sort order for keyword search (mode=search). |
| `publishedWithin` | string | Limit keyword search results by publish period (mode=search). Choose Custom to use dateFrom and dateTo. |
| `categoryNo` | integer | Naver blog category number to restrict a blog archive; 0 means all categories (mode=blogPosts). |
| `maxItems` | integer | Hard cap on emitted records across all queries, blogs, or URLs. |
| `includeContent` | boolean | Fetch each post page for full text, exact publish time, images, tags, category, and places. Turn off for faster list-level records. |
| `includeComments` | boolean | Add the comment count and comment threads up to maxComments (default 100), including replies when Naver returns them. Implies includeContent=true and adds requests per post. |
| `maxComments` | integer | Maximum comments to return per post when includeComments is on. Fetched in pages of 100; commentCount still reports the full total. |
| `includeHtml` | boolean | Add the post body as HTML in contentHtml. Implies includeContent=true. |
| `maxConcurrency` | integer | Parallel post-page requests when content enrichment is enabled. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQueries": [
    "제주도 여행"
  ],
  "sortBy": "sim",
  "publishedWithin": "all",
  "categoryNo": 0,
  "maxItems": 3,
  "includeContent": false,
  "includeComments": false,
  "maxComments": 100,
  "includeHtml": false,
  "maxConcurrency": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~naver-blog-post-search-and-full-content-extractor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~naver-blog-post-search-and-full-content-extractor/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `title`, `authorName`, `blogName`, `publishDate`, `contentLength`, `commentCount`, `likeCount`, `isSelfPurchased`, `postUrl`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.