Bing Organic Search Results Scraper: MCP config, n8n workflow and API

{
  "mode": "webSearch",
  "queries": [
    "best coffee shops seattle"
  ],
  "maxResultsPerQuery": 3,
  "market": "en-US",
  "safeSearch": "moderate",
  "dateRange": "anyTime",
  "imageSize": "any",
  "videoDuration": "any",
  "newsSort": "relevance"
}

---
name: bing-organic-search-results-scraper
description: "One record per Bing web result, news article, image, video or autocomplete suggestion, with its query, rank, page, destination URL and the details Bing shows for it. Runs the Apify Actor nimbryxo-studio/bing-organic-search-results-scraper. Use when the user needs Bing data with fields such as query, resultType, recordType, position, rank, page 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/bing-organic-search-results-scraper"
  store-url: "https://apify.com/nimbryxo-studio/bing-organic-search-results-scraper"
---

# Bing Organic Search Results Scraper

Use this skill to fetch Bing data with the Apify Actor `nimbryxo-studio/bing-organic-search-results-scraper` 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 `webSearch`, `newsSearch`, `imageSearch`, `videoSearch`, `autocomplete`, required | Which Bing surface to collect. Web returns organic web results; News, Images and Videos return that vertical; Autocomplete returns query suggestions. |
| `queries` | array | One or more searches, exactly as you would type them into Bing. Quotes and search operators work. Repeat queries are searched once. |
| `maxResultsPerQuery` | integer | Maximum records to collect for each query, across result pages. Bing may return fewer when its own list ends. |
| `market` | string | The Bing market and language to search in. Results, interface language and ranking can differ by market. |
| `safeSearch` | one of `moderate`, `strict`, `off` | Bing's adult-content filter. Moderate is Bing's own default; Strict removes adult pages and images; Off keeps everything Bing returns. |
| `dateRange` | one of `anyTime`, `past24Hours`, `pastWeek`, `pastMonth`, `pastYear` | Keep results published inside this window when Bing prints a date for them. Results without a printed date are kept. |
| `imageSize` | one of `any`, `small`, `medium`, `large` | Prefer small, medium or large images. The choice is applied through Bing's image-size filter. |
| `videoDuration` | one of `any`, `short`, `medium`, `long` | Keep short (under 5 minutes), medium (5–20 minutes) or long (over 20 minutes) videos. |
| `newsSort` | one of `relevance`, `mostRecent` | Order news articles by Bing's relevance or newest first. |

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

```json
{
  "mode": "webSearch",
  "queries": [
    "best coffee shops seattle"
  ],
  "maxResultsPerQuery": 3,
  "market": "en-US",
  "safeSearch": "moderate",
  "dateRange": "anyTime",
  "imageSize": "any",
  "videoDuration": "any",
  "newsSort": "relevance"
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~bing-organic-search-results-scraper/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~bing-organic-search-results-scraper/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: `query`, `resultType`, `recordType`, `position`, `rank`, `page`, `title`, `url`, `displayUrl`, `description`, `snippet`, `siteName`, `breadcrumb`, `dateText`, `source`, `imageUrl`, `thumbnailUrl`, `width`, `height`, `imageId`.

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