Skip to main content
Glama
adpilot-mcp

adpilot-mcp

Official
by sholaxai

apply_budget_plan

Destructive

Apply a previously proposed budget plan using its plan ID; each plan expires and can be applied only once.

Instructions

Execute a previously proposed budget plan. Plans expire and can only be applied once.

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": {
      "planId": "<planId>"
    },
    "name": "apply_budget_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

The destructiveHint annotation already flags this as a mutating operation, and the description adds genuinely new behavioral facts: plans expire and can only be applied once, so the agent knows the call is non-idempotent and time-bounded. It does not disclose what exactly is modified (which campaigns/budgets) or whether the change is reversible.

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?

Two short sentences, action first and constraints second, with no redundant wording. Every clause contributes a distinct fact.

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 destructive, single-parameter mutation with no output schema and no parameter documentation, the definition covers preconditions and lifecycle but omits what actually changes in the budget, what happens on an expired/already-used plan, and any permission requirements. Adequate but with clear gaps.

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?

The schema has 0% description coverage for planId, and the description only implies its provenance ('previously proposed budget plan') without stating the required format or where the value comes from. The regex pattern in the schema carries the format burden, so this is marginally better than schema-only.

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 ('Execute') and resource ('previously proposed budget plan'), and the word 'previously' implicitly ties it to the propose_budget_plan sibling. It stops short of naming that sibling outright, but an agent can still distinguish proposal from execution.

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?

The description establishes the precondition (a plan must already have been proposed) and two hard constraints (plans expire, single use), which effectively define when this tool can and cannot be called. It does not explicitly redirect the agent to propose_budget_plan when no planId exists.

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