Skip to main content
Glama

Alterar orçamento diário

pixel_set_budget
DestructiveIdempotent

Altera o orçamento DIÁRIO de uma campanha (CBO) ou adset Meta. Valor em CENTAVOS de BRL (integer > 0). DRY-RUN por padrão; executa só com dry_run:false. Requer plano Pro.

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": {
      "amount_cents": "<amount_cents>"
    },
    "name": "pixel_set_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNotrue ou ausente = DRY-RUN: descreve o efeito sem aplicar. false = EXECUTA a ação de fato. Só envie false após o usuário confirmar.
adset_idNoID do adset (use este OU campaign_id).
campaign_idNoID da campanha (use este OU adset_id).
amount_centsYesNovo orçamento diário em CENTAVOS de BRL (> 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / amount_cents / minimum
      Added value: +1
    • changedInput schema / properties / amount_cents / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds genuinely new behavioral context — dry-run is the default and must be explicitly disabled, and a Pro plan is required. It stops short of describing the return payload or what happens to existing budget scheduling, but the safety profile is well covered.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action and unit, then the dry-run gate and the plan requirement. Capitalized emphasis on DIÁRIO and CENTAVOS flags the two mistakes an agent is most likely to make; nothing is redundant.

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

Completeness4/5

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

For a destructive mutation with no output schema, the definition covers unit, target selection, execution gate and plan precondition. Minor gap: it does not say how to learn the current budget or what a successful mutation returns, though the dry-run mode partially compensates by describing the effect.

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, but the description adds meaning the schema does not: the amount is in CENTAVOS de BRL and applies to the daily budget of either a CBO campaign or an adset. That CBO framing clarifies what campaign_id actually controls.

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?

Uses a precise verb+resource ('Altera o orçamento DIÁRIO') and scopes the target to 'campanha (CBO) ou adset Meta', which no sibling tool touches (siblings are read/pause/resume/sync operations). An agent can identify the action and its object 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 Guidelines4/5

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

Clearly states the execution gate ('DRY-RUN por padrão; executa só com dry_run:false') and a precondition ('Requer plano Pro'), so the agent knows when the call will actually apply changes. It does not name alternative tools, but no sibling performs budget edits, so the practical risk of misrouting is low.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources