Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_budget_schedule

Create a budget schedule for a campaign or ad set by defining an absolute or multiplier budget, start time, and end time.

Instructions

Create a budget schedule on a campaign or ad set.

Input Schema

NameRequiredDescriptionDefault
time_endYesSchedule end time as a Unix timestamp
parent_idYesCampaign or ad set ID that will own the budget schedule
time_startYesSchedule start time as a Unix timestamp
parent_typeNoType of parent objectcampaign
budget_valueYesUnsigned value interpreted according to budget_value_type (ABSOLUTE uses currency minor units)
budget_value_typeYesHow budget_value is applied

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.6.1
    • changedInput schema / properties / budget_value / description
      Previous value: -"Budget amount in account currency cents"New value: +"Unsigned value interpreted according to budget_value_type (ABSOLUTE uses currency minor units)"
    • addedInput schema / properties / budget_value / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / budget_value / type
      Previous value: -"string"New value: +"integer"
    • changedInput schema / properties / budget_value_type / description
      Previous value: -"Budget value type (e.g. ABSOLUTE, MULTIPLIER)"New value: +"How budget_value is applied"
    • addedInput schema / properties / budget_value_type / enum
      Added value: +[
+  "ABSOLUTE",
+  "MULTIPLIER"
+]
    • addedInput schema / properties / parent_id
      Added value: +{
+  "description": "Campaign or ad set ID that will own the budget schedule",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / parent_type
      Added value: +{
+  "default": "campaign",
+  "description": "Type of parent object",
+  "enum": [
+    "campaign",
+    "adset"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / time_end / description
      Previous value: -"Schedule end time (ISO 8601 or Unix timestamp)"New value: +"Schedule 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: -"Schedule start time (ISO 8601 or Unix timestamp)"New value: +"Schedule 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"
    • changedInput schema / required
      Previous value: -[
-  "budget_value",
-  "budget_value_type",
-  "time_start",
-  "time_end"
-]New value: +[
+  "parent_id",
+  "budget_value",
+  "budget_value_type",
+  "time_start",
+  "time_end"
+]
  2. First observedv1.2.0

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 burden of disclosure and offers only 'create a budget schedule'. It says nothing about the mutating effects, required permissions on the parent object, validation rules (e.g. time_start before time_end), or whether an existing schedule is replaced.

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?

A single front-loaded sentence with no filler. It is efficient, though the extreme brevity is arguably under-specification rather than disciplined conciseness given the tool's complexity.

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

Completeness2/5

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

For a six-parameter mutation tool with five required fields, no annotations and no output schema, the description omits the temporal constraint linking time_start/time_end, the meaning of a MULTIPLIER versus ABSOLUTE budget, and the parent_type default. An agent could not call this correctly from the description alone.

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%, so the schema already documents all six parameters, including budget_value_type semantics and the Unix timestamp format. The description adds no parameter-level meaning beyond what the schema provides, making the baseline 3 appropriate.

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?

The description gives a specific verb ('Create') and resource ('budget schedule') plus the owning scope ('on a campaign or ad set'), so the agent knows exactly what object is produced. It does not explicitly distinguish itself from the nearby siblings (list_/update_/delete_budget_schedule), but the create verb makes the intent unambiguous.

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?

There is no guidance on when to use this tool versus update_budget_schedule, or on the precondition that a campaign/ad set must already exist. Usage can only be inferred from the tool name, and no alternative is ever named.

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

Deploy Server

Other Tools