Reconcile campaign build

Loading server catalog…. Download catalog

POSThttps://app.advarde.com/mcp

Write

Available subject to your connection’s permissions.

Description: Read an uncertain step and uniquely match its reviewed content to a newly visible Ads resource. Does not retry a create. Uploads with an unknown result require manual verification.

Method: tools/call · ads_reconcile_campaign_build

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.

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.

build_idstringrequired

format: "uuid"

resource_idstringoptional

maxLength: 255

Full JSON Schema

{
  "type": "object",
  "properties": {
    "build_id": {
      "type": "string",
      "format": "uuid"
    },
    "resource_id": {
      "type": "string",
      "maxLength": 255
    }
  },
  "required": [
    "build_id"
  ],
  "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.

REQUEST URL · POST

https://app.advarde.com/mcp

Request headers

Authorization: Bearer $ADVARDE_MCP_TOKEN
Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: 2025-03-26

Tool arguments (JSON)

These values become params.arguments in the request body. Replace sample IDs and values with your own.

Full request body

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ads_reconcile_campaign_build",
    "arguments": {
      "build_id": "00000000-0000-4000-8000-000000000001"
    }
  }
}

I reviewed and authorize this exact request to change workspace data.

RESPONSE

No request sent

The actual server response will appear here.

CODE EXAMPLE

cURL requestJSON-RPC 2.0

curl --request POST \
  --url 'https://app.advarde.com/mcp' \
  --header "Authorization: Bearer $ADVARDE_MCP_TOKEN" \
  --header 'Accept: application/json, text/event-stream' \
  --header 'Content-Type: application/json' \
  --header 'MCP-Protocol-Version: 2025-03-26' \
  --data '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "ads_reconcile_campaign_build",
    "arguments": {
      "build_id": "00000000-0000-4000-8000-000000000001"
    }
  }
}'

This endpoint uses stateless Streamable HTTP with JSON responses. Connect token performs initialization and discovery. Code examples show the individual request.