> 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/tool-reference/contacts.md). # Contacts & Tags Contacts are the people your channels message. (The REST API calls them "humans," so tool and field names use that term.) **Tags** label contacts and are how blasts pick their recipients. ## Contacts | Tool | What it does | Key inputs | | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | | `list_humans` | Page through contacts: `id`, `name`, `firstName`, `lastName`, `phoneNumber`, `subscribedChannels`, `botEnabled` | `limit`, `cursor` | | `get_human` | Full record: channels, subscriptions, custom fields, RCS capability flags, bot-enabled state | `human_id` | | `find_humans_by_attributes` | Filter contacts on a custom attribute. Operators: `present`, `absent`, `equal`, `notEqual`, `greater`, `greaterOrEqual`, `less`, `lessOrEqual` (`value` required except for present/absent). A type mismatch matches nothing rather than erroring | `attribute_name`, `operator`, `value`, paging | | `add_humans_by_phones` | Create contacts on a channel from phone numbers; each item requires `phone`, may include `firstName`, `lastName`, `userName`, `company`, `customFields`. Optionally `assign_tags` (names auto-created), `subscribe` (opted-in contacts only), `update_existing` | `channel_id`, `humans`, options | | `update_human_attributes` | Add or overwrite custom attributes (`attributeName -> value` map) | `human_id`, `attributes` | | `get_human_subscription` | Subscription state on the contact's primary channel | `human_id` | | `set_human_bot_enabled` | Turn the automated experience on/off for one contact — off is how a person takes over the conversation | `human_id`, `bot_enabled` | | `check_rcs_capability` | Whether a phone supports RCS on a given channel: `{ rbmEnabled, features[], name }` with feature codes like `RICHCARD_STANDALONE`, `RICHCARD_CAROUSEL`, `ACTION_OPEN_URL` | `phone_number`, `channel_id` | | `add_tester_device` | Register a phone as a tester on an RCS channel. The device gets an invitation it must accept; a contact is created. An unlaunched RCS agent can only message testers | `channel_id`, `phone_number` | ## Tags | Tool | What it does | Key inputs | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | | `list_tags` | All tags: `{ id, name, description, dateCreated, dateUpdated }` | paging | | `get_tag` | One tag | `tag_id` | | `create_tag` | Create a tag (`name` ≤100 unique, `description` ≤200) | `name`, `description` | | `update_tag` | Rename/re-describe. A rename also updates experiences and templates that refer to the tag by name | `tag_id`, fields | | `delete_tag` | Remove the tag from every contact and blast. Cannot be undone. Refused — with contact/blast counts — when in use, unless `force: true` | `tag_id`, `force` | | `assign_tags_to_human` | Add tags to a contact. Exactly one of `tag_names` (missing names auto-created) or `tag_ids` | `human_id`, tags | | `unassign_tags_from_human` | Remove tags from a contact | `human_id`, tags | | `get_human_tags` | Tags on one contact | `human_id` | | `list_tags_for_humans` | Distinct tags across several contacts in one call | `human_ids`, paging | | `list_humans_by_tag` | Ids of contacts carrying a tag | `tag_id`, paging | ## Notes * **Opt-in is on you:** `subscribe` and `subscribe_humans_to_channel` must only be used for contacts who have explicitly opted in. Never re-subscribe someone who opted out. * Tags drive blast targeting: a blast reaches contacts that carry any of its tags *and* are subscribed to one of its channels. --- # 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/tool-reference/contacts.md?ask=&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.