Skip to main content
Glama

Read account health

get_account_health
Read-only

Call this FIRST for any question about the account's state, spend or a drop in results. Returns the ad account's billing status, today's spend against what its live budgets should have spent by this hour, yesterday's spend, and every ad set's delivery over the last 48 hours, including ad sets that read ACTIVE but have stopped delivering and the cause when one can be named (a disapproved ad, an unsettled balance). A campaign reading ACTIVE in Ads Manager does not mean it is spending; this tool is how you tell.

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": "get_account_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint, so the description carries the real burden and does: it discloses lookback windows (48 hours), the specific fields returned, and the non-obvious interpretive rule that an ACTIVE campaign in Ads Manager may not be spending. Naming the diagnosable causes (disapproved ad, unsettled balance) tells the agent what signal to expect in the output.

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?

It is front-loaded with the imperative triage instruction, then the return contents, then the rationale. The final sentence partially restates the ACTIVE-but-not-delivering point made earlier, a slight redundancy, but it functions as the value justification rather than filler.

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?

With no input parameters and no output schema, the description must describe the return surface itself, and it does so field by field, including the delivery diagnosis and named failure causes. An agent can call this and interpret the result without further documentation.

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?

The tool takes no parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly implies a zero-argument call. It adds mild value by framing the result as account-scoped rather than parameterized.

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?

The description gives a specific verb-and-resource pair and enumerates the exact payload: billing status, today's spend versus budget pace, yesterday's spend, and 48 hours of ad set delivery. It is clearly distinguishable from reporting siblings like get_ad_insights or get_performance_report because it describes delivery-state diagnosis rather than metrics reporting.

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 states precisely when to reach for it: 'Call this FIRST for any question about the account's state, spend or a drop in results,' which gives a clear entry point and precedence. It stops short of naming alternatives or stating when not to use it, so it lands at clear-context without exclusions.

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