Campaign Cleaner MCP integration for AI agents.
Connect AI agents to Campaign Cleaner through 7 structured actions, including get campaign, send campaign, and delete campaign. Review authentication, inputs…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Campaign Cleaner integration exposes
The Campaign Cleaner Agent App exposes 7 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent retrieve the full campaign cleaner analysis payload for one saved campaign, submit an email campaign html payload for campaign cleaner analysis and processing, and delete one saved campaign cleaner campaign by campaign id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Campaign Cleaner account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Campaign Cleaner capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADRetrieve the full Campaign Cleaner analysis payload for one saved campaign.
INPUTS: campaign_id / minimize_html
send_campaignWRITESubmit an email campaign HTML payload for Campaign Cleaner analysis and processing.
INPUTS: campaign_html / campaign_name / adjust_font_colors / adjust_font_size / convert_h_to_p_tags
delete_campaignHIGH IMPACTDelete one saved Campaign Cleaner campaign by campaign ID.
INPUTS: campaign_id
get_campaign_pdf_analysisREADDownload a Campaign Cleaner PDF analysis report and return it as a transit file.
INPUTS: campaign_id
get_campaign_statusREADFetch the current processing status of one submitted Campaign Cleaner campaign.
INPUTS: campaign_id
get_creditsREADGet the remaining Campaign Cleaner credits available to the current API key.
list_campaignsREADList saved Campaign Cleaner campaigns together with their current processing status.
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
campaign_idREQUIRED- The Campaign Cleaner campaign identifier.
minimize_htmlOPTIONAL- Whether the returned campaign HTML should be minimized.
send_campaign
campaign_htmlREQUIRED- The full HTML content of the email campaign.
campaign_nameREQUIRED- The saved name of the email campaign.
adjust_font_colorsOPTIONAL- Whether Campaign Cleaner should normalize spam-triggering font colors.
adjust_font_sizeOPTIONAL- Whether Campaign Cleaner should enforce the configured font size bounds.
convert_h_to_p_tagsOPTIONAL- Whether header tags should be converted into paragraph tags.
delete_campaign
campaign_idOPTIONAL- The Campaign Cleaner campaign identifier.
get_campaign_pdf_analysis
campaign_idOPTIONAL- The Campaign Cleaner campaign identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Retrieve the full Campaign Cleaner analysis payload for one saved campaign. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaignControl Send Campaign
Submit an email campaign HTML payload for Campaign Cleaner analysis and processing. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_campaignVerify with Get Campaign Pdf Analysis
Download a Campaign Cleaner PDF analysis report and return it as a transit file. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_campaign_pdf_analysisSAFETY BOUNDARY
Operate Campaign Cleaner with explicit limits
- Authorize Campaign Cleaner with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_campaign` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Campaign Cleaner rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Campaign Cleaner task completed successfully.
CONNECTION MODEL
API key
Campaign Cleaner API key sent in the X-CC-API-Key header. Manage API keys from API Management in the Campaign Cleaner dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Campaign Cleaner.