Bring your own agent.
Use Adswell’s agent or bring your own. Give it paid-media context and tools through MCP, then let it reason, plan, and prepare account work using the models and orchestration you choose.
GTM engineering
Your agent.
Built on Adswell.
Your stack. Your logic. Real work in the ad account.
Build paid media into your GTM stack with MCP and the CLI. Bring your own agent, connect your business context, and turn it into coordinated campaign work across Google, LinkedIn, and Reddit. Adswell provides the account connections, execution workflows, and shared record underneath.
# Prepare the setup plan
$ maple setup plan --platform linkedin --brief launch-brief.md --json
# Stage the reviewed plan
$ maple setup stage --plan-id <plan-id> --confirm-token <token> --json
# Response excerpt
{
"success": true,
"command": "setup stage",
"bundle_id": "bundle-9",
"proposal_ids": ["91"]
}
# Find the draft work
$ maple proposals list --status DRAFT --platform linkedin --json
Decisions
Decisions
LinkedIn campaign setup
DraftRationale
Prepare the demo campaign from the reviewed launch brief and connected account context.
What changes
| Field | Proposed |
|---|---|
| Platform | LinkedIn Ads |
| Objective | Lead generation |
| Campaign | Target-account demos |
Build the GTM system.
We’ll handle the ad accounts.
You know which accounts matter, what a qualified opportunity looks like, and when to act. Put that logic to work. Adswell connects your systems to paid-media planning, campaign execution, and performance, so every workflow can carry your business context all the way into the account.
Compose it into your stack.
Connect CRM signals, enrichment, and planning tools to campaign workflows. Use the CLI and structured responses to compose repeatable jobs, power internal applications, and move work between systems.
One foundation for every workflow.
Keep account context, proposed changes, approvals, and outcomes together in Adswell. Every agent and workflow builds on a shared account history, and your team can see what happened and why.
Choose the interface.
Keep your architecture.
Let an agent call tools, compose commands in a script, or feed account evidence into an internal application. Use the interface that fits the system you are building.
# Start the installed server
$ maple-mcp
# Give your agent account context
list_accounts
get_capability_context
list_campaigns
get_campaign
# Prepare and track the work
plan_setup
stage_proposal
list_proposals
get_proposal
# Prepare the setup plan
$ maple setup plan --platform linkedin --brief launch-brief.md --json
# Stage the reviewed plan
$ maple setup stage --plan-id <plan-id> --confirm-token <token> --json
# Response excerpt
{
"success": true,
"command": "setup stage",
"bundle_id": "bundle-9",
"proposal_ids": ["91"]
}
# Find the draft work
$ maple proposals list --status DRAFT --platform linkedin --json
# Inspect connected accounts
$ maple accounts list --platform all --json
# Check supported operations
$ maple capabilities --platform linkedin --json
# Review campaigns
$ maple campaigns list --platform google --limit 25 --json
# Read a proposal
$ maple proposal show <proposal-id> --json
Product illustrations use example data.
Build the workflow
your team actually needs.
An account enters your ICP. A launch is ready. Pipeline starts slipping. Make those signals the beginning of a paid-media workflow, with your business logic deciding what happens next.
From launch brief to campaigns.
Bring positioning, target accounts, and budget from your planning system. Generate a coordinated campaign plan, prepare the account work, and route it to the right people for approval.
From CRM signal to paid motion.
Combine lifecycle stages, enrichment, and account scores to decide who to reach and with what message. Feed that context into audience and campaign workflows, then bring results back into your stack.
From account data to your next move.
Build a specialist agent that understands your targets and guardrails. Have it investigate performance, propose the next move, and prepare changes with the evidence your team needs to review them.
From your system
to work in the account.
-
01
Connect your stack
Connect your agent through MCP or call Adswell from the CLI. Give your workflow access to the accounts it needs.
-
02
Add your logic
Bring your CRM signals, targeting logic, and business rules. Define the goals and guardrails that guide the work.
-
03
Put the plan to work
Turn your logic into campaign plans and account changes. Route them through a shared review and execution workflow.
-
04
Close the loop
Bring execution status and performance back into your stack. Use what happened to inform the next decision.
What will you
build on Adswell?
Your agent can reason. Your systems have the context. Give them a foundation for doing the paid-media work. Build your next GTM workflow on Adswell.