# RevCent MCP Guide: `RemoveTrackingDomainFromSite`

Brief MCP-focused guide for RevCent MCP clients and agents using the `RemoveTrackingDomainFromSite` operation.

---

## Operation Summary

Operation:

```text
RemoveTrackingDomainFromSite
```

Purpose:

```text
Remove the Tracking Domain association from a RevCent Site.
```

Removing a Tracking Domain prevents the custom domain from accessing the Site's main/live deployment.

---

## When to Use

Good uses:

- disconnect a custom domain from a Site,
- stop a Tracking Domain from routing to a Site's live deployment,
- prepare a Tracking Domain to be used elsewhere,
- resolve an incorrectly attached Tracking Domain after user confirmation.

Do not use this operation to delete a Tracking Domain record, delete a Site, or change dev branch routing.

---

## Required Preparation

Before calling `RemoveTrackingDomainFromSite`:

1. Identify the exact Site ID.
2. Call `GetSite` if the current Tracking Domain attachment is uncertain.
3. Explain that removing the Tracking Domain affects live custom domain access.
4. Confirm with the user before proceeding.

---

## Input Schema

`RemoveTrackingDomainFromSite` requires a path parameter.

```json
{
  "site_id": "XXXXXXXXXXXXXXXXXXXX"
}
```

The request body is an empty object.

```json
{}
```

### Required Fields

| Field | Location | Type | Required | Description |
|---|---|---:|---:|---|
| `site_id` | Path | `string` | Yes | A 20-character Site ID. |

### Important Schema Rules

- Do not include unknown body properties.
- Removing the Tracking Domain prevents custom domain access to the main/live deployment.
- This operation does not delete the Tracking Domain record itself.

---

## Output Schema

A successful response returns the Site ID.

```json
{
  "api_call_id": "XXXXXXXXXXXXXXXXXXXX",
  "api_call_unix": 1710000000,
  "code": 1,
  "site_id": "XXXXXXXXXXXXXXXXXXXX",
  "result": "string"
}
```

---

## Example Request

Path value:

```json
{
  "site_id": "XXXXXXXXXXXXXXXXXXXX"
}
```

Body:

```json
{}
```

---

## Recommended Follow-Up

After a successful call:

1. Call `GetSite`.
2. Verify `tracking_domain` is absent or no longer the removed domain.
3. Inspect `deployment.branches.main.routing.status`.
4. Summarize the live routing state for the user.

---

## Best Practices

1. Confirm before removing custom domain access.
2. Use exact Site IDs from prior MCP results.
3. Make clear that this affects the main/live custom domain path.
4. Use `GetSiteEvents` if the user wants to review the routing change timeline.
5. Do not imply that the Tracking Domain record was deleted.

---

## Final MCP Instruction

Use `RemoveTrackingDomainFromSite` only after the user confirms that the custom domain should no longer route to the RevCent Site's main/live deployment.



---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.