meta-ads-mcp

update_budget_schedule

Update a budget schedule's start/end times or budget value by ID. Only provided fields change, enabling targeted adjustments to Meta ad campaigns.

Instructions

Update an existing budget schedule. Only provided fields will be modified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "schedule_id": "<schedule_id>"
    },
    "name": "update_budget_schedule"
  }
}

Input Schema

Name	Required	Description
`time_end`	No	New end time as a Unix timestamp
`time_start`	No	New start time as a Unix timestamp
`schedule_id`	Yes	Budget schedule ID to update
`budget_value`	No	New unsigned value interpreted according to budget_value_type
`budget_value_type`	No	How budget_value is applied

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv1.6.1Oct 21, 2026

changedInput schema / properties / budget_value / description

Previous value: -"New budget amount in account currency cents"New value: +"New unsigned value interpreted according to budget_value_type"

addedInput schema / properties / budget_value / exclusiveMinimum
```
Added value: +0
```
changedInput schema / properties / budget_value / type
```
Previous value: -"string"New value: +"integer"
```

addedInput schema / properties / budget_value_type

Added value: +{
+  "description": "How budget_value is applied",
+  "enum": [
+    "ABSOLUTE",
+    "MULTIPLIER"
+  ],
+  "type": "string"
+}

changedInput schema / properties / time_end / description

Previous value: -"New schedule end time"New value: +"New end time as a Unix timestamp"

addedInput schema / properties / time_end / exclusiveMinimum
```
Added value: +0
```

changedInput schema / properties / time_end / type

Previous value: -"string"New value: +"integer"

changedInput schema / properties / time_start / description

Previous value: -"New schedule start time"New value: +"New start time as a Unix timestamp"

addedInput schema / properties / time_start / exclusiveMinimum
```
Added value: +0
```
changedInput schema / properties / time_start / type
```
Previous value: -"string"New value: +"integer"
```

First observedv1.2.0Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden. It does disclose PATCH semantics ('Only provided fields will be modified'), which is genuinely useful, but says nothing about required permissions, whether changing a budget schedule affects live ad delivery/spend, or how an invalid or expired schedule is handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the partial-update constraint is front-loaded rather than buried. Appropriately sized for a simple update tool, though it stops short of earning a 5 by omitting any extra operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description covers the core semantics but leaves gaps: success/failure behavior, permission requirements, and side effects on active spend are all unstated. The fully documented schema compensates only for parameter questions, not behavioral ones.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% – every parameter, including the budget_value/budget_value_type enum pairing, is documented in the schema itself. The description adds only the partial-update rule, which is behavioral rather than parameter-level, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Update') and resource ('budget schedule'), which clearly distinguishes it from the sibling create/list/delete_budget_schedule tools. It does not explicitly name or contrast those siblings, but the name-plus-description pair is unambiguous about intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus create_budget_schedule or delete_budget_schedule, and no prerequisites or exclusions. 'Update an existing budget schedule' implies the record must already exist, but that requirement is left for the agent to infer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server