Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

google_ads_campaigns_get

Retrieve full campaign details by ID, including dates, network settings, geo-targeting, and bidding strategy status. Use this to inspect a specific campaign when you already have its campaign ID.

Instructions

Fetches the full detail record for a single campaign by ID. Returns the same fields as campaigns.list plus start_date, end_date, network_settings, geo_target_type, and bidding_strategy_system_status. Read-only. Use this when you already have a campaign_id; for discovery use google_ads_campaigns_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign ID as returned by campaigns.list (numeric string, e.g. '23743184133').
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.10.11
  3. Removedv0.10.9
  4. Addedv0.9.12
  5. Removedv0.9.6
  6. Addedv0.9.2
  7. Removedv0.9.1
  8. Addedv1.0.5

TDQS

A4.4/5.0
Behavior4/5

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

Even though no annotations are provided, the description explicitly states 'Read-only' and explains the return field set relative to campaigns.list. It doesn't detail error behavior or rate limits, but for a read-only get operation, this is adequate behavioral disclosure.

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 three sentences with no wasted words. It front-loads the main purpose, adds return field details, and closes with usage guidance. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple get tool with no output schema, the description is fairly complete. It specifies the additional fields over campaigns.list, notes read-only behavior, and gives usage context. Minor gap: it doesn't list all fields from campaigns.list, but leveraging sibling knowledge is acceptable.

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 coverage is 100%, with both parameters already fully described. The description repeats some of that information (e.g., campaign_id from campaigns.list, customer_id fallback) but doesn't add significant new meaning beyond what the schema provides. Baseline 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's function with a specific verb and resource: 'Fetches the full detail record for a single campaign by ID.' It also distinguishes itself from sibling tools by listing additional fields returned and explicitly contrasting with google_ads_campaigns_list.

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 provides explicit usage guidance: 'Use this when you already have a campaign_id; for discovery use google_ads_campaigns_list.' This clearly indicates when to use this tool vs the alternative.

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