bouncer

Bouncer through One

A cloud-based platform that verifies and cleans email lists by identifying invalid, risky, or disposable email addresses to improve deliverability, reduce bounce rates, and enhance email campaign performance.

One exposes Bouncer through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

1. Find the action in the table below, or call search_one_platform_actions with platform bouncer if it is not listed.
2. Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
3. Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm Bouncer is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.

Before a write

Creates, updates, deletes and sends land on a real Bouncer account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.

Actions

ToxicityListJob

Action	Method	Path	Action id
Check Toxicity List Job Status	GET	/v1/toxicity/list/{{ID}}	conn_mod_def::GJt2_yOF4b8::lk0kG1xvSwCGjTbcjiRnTg
Create Toxicity List Job	POST	/toxicity/list	conn_mod_def::GJt2_qnzVsc::oM2wSVqbQk2C4s78_u2o1w
Delete a Toxicity List Job	DELETE	/v1/toxicity/list/{{id}}	conn_mod_def::GJt2_5jg-88::_4wxHQGYRtGUgPnX3sNOJA