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

# Search Signals

> Search website, market, and LinkedIn activity in your workspace.

Use `signal_at` to search when an activity occurred. Website signal payloads include `website.attribution`, `website.utm`, and `website.click_ids`. See [Search & Pagination](https://docs.1eye.ai/mcp/search-and-pagination.md) for supported filters and [Workflow examples](https://docs.1eye.ai/mcp/workflows.md) for reporting patterns.

The examples below are MCP tool arguments. Replace uppercase IDs with values returned by your workspace.

## `search_signals`

**Read-only**

Search website, market, and LinkedIn activities.

Use `signal_at` for occurrence dates. Type-specific fields and `trigger` need a compatible top-level `signal_type` rule in an `all` group. Signal totals count activities, not distinct people.

### Arguments

| Argument | Type | Required | Description |
| - | - | - | - |
| `filter` | object | Yes | Rule group containing at least one rule. See the [signal filter reference](https://docs.1eye.ai/mcp/search-and-pagination.md#signal-filter-reference). |
| `limit` | number | No | Page size; defaults to 25. |
| `cursor` | string | No | Continuation cursor from this search. |
| `sort_order` | `asc` or `desc` | No | Oldest or newest first; defaults to `desc`. |

### Example

```json theme={null}
{
  "filter": {
    "match": "all",
    "rules": [
      {
        "field": "signal_type",
        "operator": "eq",
        "value": "website"
      },
      {
        "field": "signal_at",
        "operator": "in_last",
        "value": {
          "unit": "day",
          "value": 7
        }
      }
    ]
  },
  "limit": 25
}
```

**Returns:** A paginated payload with `total`, `data`, `next_cursor`, and `applied_filter`. Each signal identifies its `buyer_id`, type, and event timestamp (`captured_at`), with the relevant website, market, or LinkedIn activity details.


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