> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bigdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# bigdata_get_monitor

> List your search monitors, filter them by name, or fetch one monitor by ID.

## Overview

The `bigdata_get_monitor` tool reads search monitors from your Bigdata.com account. It has three modes depending on what you pass:

* **List mode** (no arguments): returns every monitor, as summaries
* **Name mode** (`name`): returns summaries of the monitors whose name contains the given text, ignoring case
* **Fetch mode** (`id`): returns the full detail of one monitor

## When to Use

Get Monitor is ideal for:

* **Discovering monitors:** Finding out which monitors exist before editing, simulating, or deleting one
* **Resolving an ID:** Turning a monitor name into the `id` required by the other monitor tools
* **Checking configuration:** Reading the schedule, entities, schema, and status of a monitor

> [!TIP]
>
> Never guess a monitor ID. List or search by name first, then fetch by `id`.

## How It Works

1. **List** monitors, or search by `name`
2. **Pick** the monitor and take its `id`
3. **Fetch** it with that `id` to load the full detail

## Parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `id` | string | No | Monitor ID. Returns one monitor detail. |
| `name` | string | No | Text the monitor name must contain. Case-insensitive. |

### Important Notes

* `id` and `name` cannot be sent together
* List and name mode return summary rows only. Fetch by `id` for the full detail
* An unknown monitor `id` returns a not-found error

## Data Returned

`structuredContent` is always `{"monitors": [ ... ]}`.

**List and name mode** return one summary row per monitor:

| Field | Description |
| - | - |
| `id` | Monitor ID |
| `name` | Display name |
| `intent` | The intent the monitor was created from |
| `status` | `active` or `inactive` |
| `created_at` | Creation time |

```json theme={null}
{
  "monitors": [
    {
      "id": "b0253b18-0dd8-4a01-a9a4-f209bce91a26",
      "name": "Anthropic – Regulatory Watch",
      "intent": "Track regulatory scrutiny of Anthropic PBC: any government, regulator, legislator or competition authority action aimed at Anthropic. Capture new or escalating investigations, probes, inquiries and information requests (e.g. FTC, DOJ, SEC, CMA, European Commission, EU AI Office, national data protection authorities), antitrust or merger reviews of Anthropic deals and investments, enforcement actions, fines, consent orders, regulator-filed lawsuits, government designations or restrictions (e.g. procurement bans, supply-chain risk designations, export controls), congressional or parliamentary hearings and letters targeting Anthropic, and compliance obligations or findings under AI laws such as the EU AI Act. For each event extract: the regulator or government body, jurisdiction, type of action, status/stage, the issue at stake, potential penalties or consequences, and the date.",
      "status": "inactive",
      "created_at": "2026-11-10T09:55:19.572327Z"
    }
  ]
}
```

**Fetch mode** returns the full [monitor detail](https://docs.bigdata.com/mcp-reference/tools/bigdata-create-monitor.md#data-returned) as the only item in `monitors`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.