Skip to main content
Glama

Budget pacing and month-end forecast

meta_insights_get_budget_pacing
Read-only

This month's ad spend pacing: spend to date, run-rate month-end projection, monthly budget, status (on_track / over / under / no_budget), the daily spend needed to land on budget, and projected conversions, revenue, ROAS and CPA. All ads plus Google and Meta separately, in the reporting currency. Use for "will we hit budget", "are we overspending", "month-end forecast".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "meta_insights_get_budget_pacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
daysNo
limitNo
actionNo
statusNo
date_toNo
page_idNo
sort_byNo
user_idNo
platformNo
site_urlNo
client_idNo
date_fromNo
ad_accountNo
ig_user_idNo
user_emailNo
window_daysNo
range_presetNo
activity_onlyNo
campaign_nameNo
property_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / platform
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Platform"
      +}
    • addedInput schema / properties / window_days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Window Days"
      +}
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the forecast methodology as a run-rate projection, the exact status categories including no_budget, and that results are split across all ads, Google, and Meta in reporting currency. It still leaves some behavioral assumptions unstated, such as how the month window is defined and what happens under partial-month data, but it adds meaningful context.

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?

The description is two tight sentences: the first front-loads what the tool returns, and the second lists natural-language use cases. Every phrase contributes either output detail or selection guidance, with no filler.

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?

The output side is well covered, especially since an output schema exists, and the annotations cover safety. However, for a 21-parameter tool with no schema descriptions, the definition is materially incomplete because it does not explain how to scope or filter the request using date, platform, account, campaign, or other optional parameters.

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

Parameters1/5

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

With 21 parameters and 0% schema description coverage, the description provides essentially no guidance on parameter meaning, defaults, interactions, or which filters control the month, platform split, account scope, or pagination. Phrases like "this month's" and "Google and Meta separately" are not mapped to any specific parameters, leaving invocation semantics unclear.

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 clearly identifies the resource as monthly ad spend pacing and lists the exact metrics returned: spend to date, run-rate projection, budget, status, daily spend needed, and projected conversions/revenue/ROAS/CPA. It does not explicitly distinguish itself from the closest sibling, budgets_get_pacing, but the purpose is otherwise concrete.

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?

It gives clear intended questions such as "will we hit budget", "are we overspending", and "month-end forecast", which tell an agent when to select it. It does not provide exclusions, prerequisites, or an explicit alternative tool, so it falls short of a 5.

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.