Plan money

Loading server catalog…. Download catalog

POSThttps://app.advarde.com/mcp

Read

Available subject to your connection’s permissions.

Description: Convert an explicit decimal amount into exact budget/bid micros in the connected account currency. No currency conversion or inferred amounts. CPM units differ between individual and bulk endpoints.

Method: tools/call · ads_plan_money

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: Read access to the relevant workspace and account.

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_idstringrequired

format: "uuid"

amountstringrequired

pattern: "^\\d+(\\.\\d+)?$"

currencystringrequired

pattern: "^[A-Z]{3}$"

purposeenumrequired

enum: ["budget","cpm","cpc","cpa"]

objectiveenumoptional

enum: ["impressions","clicks","conversions"]

wire_formatenumoptional

enum: ["single","bulk"]

Full JSON Schema

{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "string",
      "format": "uuid"
    },
    "amount": {
      "type": "string",
      "pattern": "^\\d+(\\.\\d+)?$"
    },
    "currency": {
      "type": "string",
      "pattern": "^[A-Z]{3}$"
    },
    "purpose": {
      "enum": [
        "budget",
        "cpm",
        "cpc",
        "cpa"
      ]
    },
    "objective": {
      "enum": [
        "impressions",
        "clicks",
        "conversions"
      ]
    },
    "wire_format": {
      "enum": [
        "single",
        "bulk"
      ]
    }
  },
  "required": [
    "account_id",
    "amount",
    "currency",
    "purpose"
  ],
  "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.