Create conversion event setting
Loading server catalog…. Download catalog
https://app.advarde.com/mcpUpstream account eligibility and feature access may also apply.
Description: Prepare a reviewable change: Create a conversion event setting for the currently authenticated ad account.. Returns a change_id; call ads_apply_change to execute after approval. Some features need Ads account enablement.
Method: tools/call · ads_create_conversion_event_setting
Output: Tool data is returned in result.structuredContent and as JSON text in result.content. Inspect result.isError before using the result. Individual output fields depend on the operation.
Access: Requires the applicable write scopes, workspace role, and account permissions.
Upstream operation: POST /conversions/event_settings. Call this through the MCP tool above.
Review before applying
This tool prepares a proposal. Review the exact payload and obtain authorization before calling ads_apply_change. Preparation does not mean the upstream change has been applied.
Authentication
Use an MCP access token from MCP connections, or connect through OAuth. Send your token in the Authorization: Bearer header.
For full protocol initialization and tool discovery, use an MCP client. These examples show individual JSON-RPC requests.
Tool arguments
Send these fields inside params.arguments. The tool name is sent as params.name.
account_idstringrequiredWorkspace-owned Advarde connection ID from ads_list_accounts.
"uuid"bodyobjectrequiredfalseEXPAND BODY
namestringrequired1event_typestringrequired1custom_event_namestringoptional1attribution_window_daysintegerrequiredsource_idsarrayrequired1EXPAND SOURCE_IDS
Each array item
{
"type": "string"
}Full JSON Schema
{
"type": "object",
"properties": {
"account_id": {
"type": "string",
"format": "uuid",
"description": "Workspace-owned Advarde connection ID from ads_list_accounts."
},
"body": {
"properties": {
"name": {
"type": "string",
"minLength": 1
},
"event_type": {
"type": "string",
"minLength": 1
},
"custom_event_name": {
"type": "string",
"minLength": 1
},
"attribution_window_days": {
"type": "integer"
},
"source_ids": {
"items": {
"type": "string"
},
"type": "array",
"minItems": 1
}
},
"type": "object",
"required": [
"name",
"event_type",
"attribution_window_days",
"source_ids"
],
"x-openai-class-name": "sofa.api.params.conversion_event_settings.CreateConversionEventSettingBody",
"additionalProperties": false
}
},
"required": [
"account_id",
"body"
],
"additionalProperties": false
}Responses
200Successful protocol response
Inspect result.isError for tool-level failures, even when the HTTP status is 200.
202Notification accepted
MCP notifications return no JSON-RPC response body.
400Invalid request
Check the JSON-RPC envelope, parameters, and protocol version.
406Not acceptable
Accept must include application/json and text/event-stream.
429Rate limited
Wait for the Retry-After interval before making another request.
401Unauthorized
A valid, unexpired MCP bearer token is required.
403Access denied
Your connection needs access to this workspace and the requested operation.