Headless
Build your agentic suite on Concord's advertising tools
Concord built its agentic tools for advertising: reporting, targeting, media plans, platform actions, optimization. Use them in the Concord workspace, or let your own agents call them over MCP, with the same validation, permissions and approvals.
Your side
Your agents · Internal tools · Workflows · Concord workspace
Concord's agentic tools for advertising
Reporting · Targeting · Platform actions · Validation · Permissions · Approvals
Direct platform integrations
DV360 · Meta · TikTok · Snapchat · Amazon DSP · Google Ads
Agentic tools
Built by Concord, for advertising
General-purpose agents know language. These tools know media buying: platform objects, required parameters, IDs, limits. Each one is a tool Concord's own agent uses every day.
Reporting
Pull delivery and results from every connected platform.
runReportsearchPlatformEntitiesqueryDatarenderChart
Media plans and files
Read a plan as your team wrote it, write the sheet back.
readXlsxSheetreadFileContentwriteXlsxFile
Targeting
Resolve audiences and locations to platform IDs, estimate reach.
resolveTargetingsaveTargetingListdeliveryEstimate
Platform actions
Build campaigns, ad groups and ads, checked before anything is sent.
preparePlatformActionduplicateMetaEntitycreateGoogleAdsConversionAction
Optimization
Find what under-delivers and prepare the reallocation.
runOptimizationaggregateData
Automations and dashboards
Put the recurring work on a schedule, keep its results in view.
upsertAutomationsaveDashboardsaveWidget
MCP
Your agents, on top
Connect any MCP client with OAuth. Your agents describe the outcome; Concord picks the tools, loads your Skills, and prepares the work for your team to approve.
askConcord
Delegate a task in plain language. Concord runs it with its advertising tools and returns the result, or the platform actions waiting for approval.
prepareUpload · attachUpload
Hand over the files the work needs: a media plan, a creative, a list. They reach Concord the way an upload in the workspace does.
Your suite, one layer
Keep the interpretation in your own agents and workflows. Concord stays the layer that knows how each platform works, and the one that is governed.
Interpretation is yours. Execution is Concord's.
Your applications and agents can interpret intent however they like. Media buying execution still requires domain-specific tools: platform knowledge, required parameters, object hierarchies, validation, quotas, and approvals. That is the layer Concord provides.
Governance
Same controls for every caller
Headless does not mean ungoverned. Permissions, advertiser rules, limits, and approval thresholds apply whether the request comes from a person in the workspace or an agent over MCP.
Every action lands in the same auditable history, and data reached over MCP is treated exactly like workspace data: never used to train models, never shared between clients.
History
Recap of the action groups submitted to the platforms for Northlane Media.
| Advertiser | Campaign | User | Created | Updated | Submitted | ||
|---|---|---|---|---|---|---|---|
| IKEA_FR_Spring_Display_Awareness | 24 | 0 | 17 Jul, 14:49 | ||||
| Nike_AirMax_Summer_Video | 0 | 8 | 17 Jul, 10:02 | ||||
| Loreal_Glow_Q3_YouTube | 13 | 0 | 16 Jul, 13:21 | ||||
| IKEA_Always_On_Display | 0 | 1 | 16 Jul, 09:26 | ||||
![]() | Samsung | Samsung_Galaxy_Launch_Reach | 29 | 0 | 15 Jul, 13:04 | ||
| IKEA_Spring_Social_Prospecting | 2 | 0 | 15 Jul, 12:53 |
Questions
Questions developers ask
Can our own agents use Concord?
- Yes. Connect any MCP client with OAuth. Your agents describe the outcome; Concord picks the tools, loads your Skills, and prepares the work for your team to approve.
What is askConcord?
- askConcord is the MCP tool your agents use to delegate a task in plain language. Concord runs it with its advertising tools and returns the result, or the platform actions waiting for approval.
Do agents connected over MCP follow different rules?
- No. Permissions, advertiser rules, limits and approval thresholds apply whether the request comes from a person in the workspace or an agent over MCP, and every action lands in the same auditable history.
Where is the developer documentation?
- On docs.concord.ad, which documents the Concord MCP server and its tools.
The same tools as the Concord workspace, called by your agents.

