# Remove or block leads

> Remove leads you do not want, or keep a company or person out of your automations.

Every section below does the same job: in the dashboard (Guide), from your code (API) or through an AI assistant (MCP).

## Guide — In the dashboard

Source: /docs/leads/hide-delete

Clean up your leads: remove one, delete several at once, or block a company or person from every automation.

<DemoFrame guide="leads-hide-delete" to="/identify/{workspace}?tab=visitors" />

1. **⋮ on a lead → Remove Lead** (you confirm).
2. **Block company / person** keeps them out of automations.
3. **Tick several → trash** deletes them together.


---

## API — From your code

Source: /docs/leads/hide-delete/api

Authenticated with `?privateKey=YOUR_KEY` (see [Authentication](/docs/authentication)).

<Endpoints ops={["POST /v3/leads/{leadId}/hide", "POST /v3/leads/delete"]} />

<ApiPlayground
  ops={["POST /v3/leads/{leadId}/hide", "POST /v3/leads/delete"]}
  method="post"
  path="/v3/leads/{leadId}/hide"
  tool="hide_lead"
  args={`{
  "leadId": "",
  "hide": true
}`}
/>

### Use case: Hide test leads [#use-case-hide-test-leads]

`POST /v3/leads/{leadId}/hide` with `{ "hide": true }` hides one lead; `POST /v3/leads/delete` with `{ "leadIds": [...] }` deletes several for good.


---

## MCP — AI agents

Source: /docs/leads/hide-delete/mcp

Connect the [MCP server](/docs/mcp#quickstart), then just ask.

<Tools names={["hide_lead", "delete_lead"]} />

### Use case [#use-case]

> Hide the leads from our own office.

<McpToolCall name="hide_lead">

```json
{
  "leadId": "6530c1d2e3f4a5b6c7d8e9f2",
  "hide": true
}
```

</McpToolCall>