Skip to main content
Glama

google_ads_monitoring_delivery_goal

Check if a Google Ads campaign is actively delivering by assessing diagnostics and yesterday's performance metrics. Returns status and actionable recommendations when delivery issues are detected.

Instructions

Check whether a Google Ads campaign is actively delivering yesterday by composing campaign info, delivery diagnostics, and yesterday's performance. Returns {campaign_id, campaign, diagnosis:{issues, warnings, recommendations, ...}, performance (list of yesterday rows with metrics), status ('critical'|'warning'|'healthy'), issues:[strings], summary, suggested_workflow?}. 'critical' fires when delivery diagnostics have issues, the campaign is not ENABLED, or yesterday impressions == 0. 'warning' fires for diagnostic warnings or impressions 1-9. suggested_workflow is set to 'delivery_fix' when status != 'healthy'. Read-only. For the raw diagnostics without the yesterday composite use google_ads_campaigns_diagnose; for CPA-target evaluation use google_ads_monitoring_cpa_goal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
Behavior5/5

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

Despite no annotations, the description fully discloses the return structure, status conditions, and declares the tool as read-only. It explains the logic for 'critical', 'warning', and 'healthy' statuses.

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?

The description is well-structured with purpose first, then return details, status logic, and alternatives. It is slightly verbose but every sentence adds value.

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?

The description is comprehensive: it covers purpose, output structure, status conditions, and alternative tools. No output schema exists, but the return format is fully described.

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?

Input schema has 100% coverage with clear descriptions. The description does not add additional semantics beyond what the schema provides, so baseline score of 3 is appropriate.

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 clearly states the tool checks campaign delivery status with a composite of info, diagnostics, and performance. It distinguishes from siblings like google_ads_campaigns_diagnose and google_ads_monitoring_cpa_goal.

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?

The description explicitly provides alternatives for raw diagnostics (google_ads_campaigns_diagnose) and CPA-target evaluation (google_ads_monitoring_cpa_goal), guiding the agent on when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server