Metadata MCP Connector

Create or Update Budget Group

create_budget_group

Destructive

Create or update a budget group with its channel, metric, allocation, and budget settings. This can affect advertising spend and requires confirm_budget_impact=true for the supplied settings; otherwise returns requires_confirmation and proposed_changes without writing. An id selects an existing group for update. Data containing only id and monthlyCap changes the monthly cap alone: it preserves the group's saved optimization, dates, funnels and campaigns and returns budget_update_verification; report success only when verified is true, and stop without retrying when it is false. New groups default autoApplyBudget to false; explicit autoApplyBudget=true allows the platform to apply the configured budget automatically. On create, omitting autoPauseConfigurationId uses the account's default auto pause rule set; on update, omitting it keeps the current one, and a different rule set must be one listed by get_budget_group. Returns the group or a validation/platform error.

Input Schema

Name	Required	Description	Default
`data`	Yes	Budget group configuration
`confirm_budget_impact`	No	Explicit authorization for these spend changes. False returns a confirmation request without writing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / confirm_budget_impact

Added value: +{
+  "default": false,
+  "description": "Explicit authorization for these spend changes. False returns a confirmation request without writing.",
+  "type": "boolean"
+}

changedInput schema / properties / data / properties / autoApplyBudget / default
```
Previous value: -trueNew value: +false
```

Changed2 schema fields changedOct 7, 2026

removedInput schema / properties / data / properties / autoPauseConfigurationId / default
```
Removed value: -14
```

addedInput schema / properties / data / properties / autoPauseConfigurationId / description

Added value: +"The id of one of the account's own auto pause rule sets (get_budget_group lists them), only when the user chose it. On create, omit it to use the account's default rule set, which covers Lead Generation and Brand Awareness alike; on update, omit it to keep the group's current rule set."

Changed8 schema fields changedOct 5, 2026

addedInput schema / properties / data / anyOf

Added value: +[
+  {
+    "minProperties": 2,
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "id"
+      ]
+    },
+    "properties": {
+      "monthlyCap": {
+        "minimum": 1
+      }
+    },
+    "required": [
+      "name",
+      "budgetType",
+      "monthlyCap",
+      "goal",
+      "budgetRedistributionStrategy"
+    ]
+  }
+]

addedInput schema / properties / data / properties / id / minimum
```
Added value: +1
```

changedInput schema / properties / data / properties / monthlyCap / description

Previous value: -"Monthly spending cap in USD"New value: +"User-confirmed monthly spending cap in USD. Zero is allowed on updates, subject to the platform's already-spent guard."

changedInput schema / properties / data / properties / monthlyCap / minimum
```
Previous value: -1New value: +0
```
removedInput schema / properties / data / properties / optimizerFormula / default
```
Removed value: -"CPL_2"
```

changedInput schema / properties / data / properties / optimizerFormula / description

Previous value: -"CPL_2 (or CPC_2) for Lead Gen; MQL for an MQL-optimized Lead Gen group (with groupMetric=CPMQL); CPC_2 or CTR for Brand Awareness."New value: +"CPL_2 (or CPC_2) for Lead Gen; MQL for an MQL-optimized Lead Gen group (with groupMetric=CPMQL); CPC_2 or CTR for Brand Awareness. INFLUENCED_OPP for influenced-opportunity optimization with goal=CPL. Omit on cap-only updates to preserve the stored formula."

changedInput schema / properties / data / properties / optimizerFormula / enum

Previous value: -[
-  "CPL_2",
-  "MQL",
-  "CPC_2",
-  "CTR"
-]New value: +[
+  "CPL_2",
+  "MQL",
+  "CPC_2",
+  "CTR",
+  "INFLUENCED_OPP"
+]

removedInput schema / properties / data / required

Removed value: -[
-  "name",
-  "budgetType",
-  "monthlyCap",
-  "goal",
-  "budgetRedistributionStrategy"
-]

Changed6 schema fields changedSep 17, 2026

changedInput schema / properties / data / properties / goal / description

Previous value: -"Optimization goal. CPL/MQL for Lead Gen; CTR for Brand Awareness."New value: +"Optimization goal. CPL for Lead Gen (MQL-optimized groups included); CTR for Brand Awareness."

changedInput schema / properties / data / properties / goal / enum

Previous value: -[
-  "CPL",
-  "MQL",
-  "CTR"
-]New value: +[
+  "CPL",
+  "CTR"
+]

changedInput schema / properties / data / properties / groupMetric / description

Previous value: -"Group metric. CPL/MQL for Lead Gen; CPC or CTR for Brand Awareness (match optimizerFormula)."New value: +"Group metric. CPL (cost per lead) or CPMQL (cost per MQL) for Lead Gen; CPC or CTR for Brand Awareness (match optimizerFormula)."

changedInput schema / properties / data / properties / groupMetric / enum

Previous value: -[
-  "CPL",
-  "MQL",
-  "CPC",
-  "CTR"
-]New value: +[
+  "CPL",
+  "CPMQL",
+  "CPC",
+  "CTR"
+]

changedInput schema / properties / data / properties / optimizerFormula / description

Previous value: -"CPL_2/CPC_2 for Lead Gen; CPC_2 or CTR for Brand Awareness."New value: +"CPL_2 (or CPC_2) for Lead Gen; MQL for an MQL-optimized Lead Gen group (with groupMetric=CPMQL); CPC_2 or CTR for Brand Awareness."

changedInput schema / properties / data / properties / optimizerFormula / enum

Previous value: -[
-  "CPL_2",
-  "CPC_2",
-  "CTR"
-]New value: +[
+  "CPL_2",
+  "MQL",
+  "CPC_2",
+  "CTR"
+]

First observedSep 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare destructive/openWorld, and the description adds real context beyond them: the spend-impact confirmation gate, the requires_confirmation non-writing path, and the budget_update_verification contract with an explicit 'stop without retrying when false' instruction. The only thing missing is more on the returned error/validation shape, which it summarizes in one clause.

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?

Front-loads the create/update contract and confirmation gate, and each paragraph carries operational meaning. It is dense but slightly overlong, with some overlap between the description and the already-documented autoPauseConfigurationId schema text.

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

Completeness5/5

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

For a destructive, open-world mutation with a nested 2-parameter schema, it covers creation, update, cap-only updates, confirmation, verification, and default resolution of the pause rule set, plus a one-line return summary. An agent has everything needed to call it and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns extra by explaining defaults and semantics not obvious from the schema, e.g. autoApplyBudget defaults to false and must be explicitly true for platform application, and autoPauseConfigurationId is defaulted on create but retained on update. It partially restates the schema's own field descriptions, which caps it below 5.

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

Purpose5/5

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

States a specific verb pair and resource ('Create or update a budget group') plus the fields it carries (channel, metric, allocation, budget settings). It explicitly distinguishes create from update via the presence of 'id', so an agent can route correctly without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit conditions: an id selects an existing group for update, data with only id+monthlyCap is a cap-only update, and confirm_budget_impact=true is required or the call returns without writing. It also points to get_budget_group as the source for valid auto pause rule sets, naming the alternatives an agent needs.

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

All Metadata MCP Connector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?