> For the complete documentation index, see [llms.txt](https://playbook.nativemsg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.nativemsg.com/mcp/versioning.md).

# Versioning & Deprecations

## How the tool surface evolves

* **Additive by default.** New tools and new optional parameters appear without notice and never break an existing integration.
* **Renames and removals get a deprecation cycle.** A deprecated tool keeps working for at least one release cycle, with its description updated to name its replacement, before removal. Deprecations are announced here and in the changelog.
* Your AI client refreshes the tool list each session, so additions show up automatically.

## Current deprecations

| Deprecated  | Use instead        | Status                                                                                                |
| ----------- | ------------------ | ----------------------------------------------------------------------------------------------------- |
| `list_bots` | `list_experiences` | Deprecated — bots are now called **experiences**. Working, slated for removal after the current cycle |
| `get_bot`   | `get_experience`   | Same                                                                                                  |

If you have saved prompts, agent instructions, or skills that name the old tools, update them to the `*_experience` names now.

## Changelog

**November 2026**

* Experiences: full lifecycle added — `create_experience`, `update_experience`, `delete_experience`, `list_experiences`, `get_experience`, plus revisions (`list_experience_revisions`, `get_experience_revision`, `restore_experience_revision`)
* Create/update/delete added for channels, blasts, tags, webhooks, and message templates (18 tools)
* `list_bots` / `get_bot` deprecated in favor of experience naming
* Tool count: 50 → 73

**Earlier**

* Initial release: contacts, tags, channels, RCS sends, templates, blast operations, delivery status, read-only bots and webhooks (50 tools)

## Checking what's live

The authoritative list is always the server itself: `tools/list` via your MCP client, or

```bash
npx @modelcontextprotocol/inspector --cli https://mcp.nativemsg.com/mcp --transport http --method tools/list
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://playbook.nativemsg.com/mcp/versioning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.