Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_monitoring_delivery_goal

Check whether a Google Ads campaign is actively delivering yesterday by combining campaign info, diagnostics, and performance data, and return a status with issues and recommendations.

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'|'unknown'), 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. 'unknown' when a part could not be retrieved and nothing that was read is critical. suggested_workflow is set to 'delivery_fix' when status is 'critical' or 'warning'. A part that could not be retrieved is null and named in issues, and nothing is derived from it. 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

NameRequiredDescriptionDefault
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  2. Addedv0.9.12
  3. Removedv0.9.6
  4. Addedv0.9.2
  5. Removedv0.9.1
  6. Addedv1.0.5

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so: it declares 'Read-only', spells out the status derivation rules (critical = diagnostic issues / non-ENABLED / zero impressions; warning = warnings or 1-9 impressions; unknown = unretrievable part), and states that partial failures yield null and are named in issues with nothing derived from them.

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?

Purpose and return shape are front-loaded, and the status rules plus fallback semantics earn their sentences. It is dense and slightly packed — the status thresholds could be tightened — but there is no 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?

No output schema exists, so the description supplies the return contract itself: the object shape, per-status trigger conditions, suggested_workflow behavior, and the null/partial-retrieval rule. Nothing an agent needs to interpret the result is missing.

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?

Schema description coverage is 100%, with both campaign_id and customer_id fully documented in the schema (format, example, fallback to env vars). The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource — check whether a campaign is actively delivering yesterday — and explicitly composes campaign info, diagnostics, and yesterday's performance. It is cleanly separable from google_ads_campaigns_diagnose and google_ads_monitoring_cpa_goal, which it names.

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?

Gives the selecting condition inline ('actively delivering yesterday') and routes to two named alternatives with their own conditions: raw diagnostics go to google_ads_campaigns_diagnose, CPA-target evaluation to google_ads_monitoring_cpa_goal. An agent can pick the right tool without opening any sibling schema.

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

Deploy Server

Other Tools