---
title: "Call ads.set_budget"
method: POST
path: "/api/v1/tools/ads.set_budget"
tags: ["ads"]
---

# Call ads.set_budget

`POST /api/v1/tools/ads.set_budget`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/ads.set_budget`
- Auth: HTTP bearer

Set what a campaign spends and for how long, or how many ads it tries — 'make it $40 a day', 'run it for two weeks from Monday', 'no end date', 'try five ads instead'. Saves the daily amount in dollars, the first and last day, or the ad count onto the campaign's Budget step; anything not named stays as it is. Nothing spends until the campaign launches, and a higher ad count draws nothing by itself. A campaign that is already live is refused. Not for launching the campaign — that is `ads.approve_launch`.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with `workspace_ambiguous` and lists the choices — offer them, never pick one.

## Headers

- `x-request-id` string

## Request body

- object
  - `campaign_id` string, uuid: The campaign's id. Leave it out to use the campaign the person is looking at.
  - `daily_budget_dollars` number: The daily amount in DOLLARS, e.g. 40 for $40 a day — never cents. Leave it out to keep the current amount.
  - `starts_on` string: The first day, YYYY-MM-DD, only when the person names one. Leave it out to keep the current start.
  - `ends_on` string: The last day, YYYY-MM-DD, only when the person names one. Leave it out to keep the current end.
  - `run_until_paused` boolean: true only when the person wants no end date — the campaign then runs until they pause it.
  - `ad_count` integer: How many ads the campaign should try, only when the person names a number. It draws nothing by itself.
  - `workspace` string: Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

## Response `200`

The call was admitted and dispatched. `ok` says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `daily_budget_cents` integer, required
    - `total_cents` integer, nullable, required
    - `starts_on` string, nullable, required
    - `ends_on` string, nullable, required
    - `ad_count` integer, required
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)