Skip to main content
Glama
Sign In
Google Ads MCP Server

Google Ads MCP Server

by nexoradev-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_campaign

Read-only

Retrieve details for a single Google Ads campaign by providing the customer ID and campaign ID, so you can inspect its settings and status.

Instructions

Get details for a single campaign.

Args:
    customer_id: Google Ads customer ID.
    campaign_id: The campaign ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_id": "<customer_id>",
      "campaign_id": "<campaign_id>"
    },
    "name": "get_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes
customer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say what happens when the campaign is not found, what fields come back, or whether cross-account access matters.

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 summary sentence is front-loaded and short. The Args block largely duplicates schema titles, which is minor waste but keeps the definition easy to scan.

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?

This is a single-resource read with no output schema, so the description should at least sketch what 'details' include or note failure behavior for an unknown campaign ID. Neither is present, leaving the agent under-informed relative to tool complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only clarifies that customer_id is a 'Google Ads customer ID' — useful but minimal — while 'campaign_id: The campaign ID' merely restates the field title with no format or source guidance.

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 states a specific verb and resource: 'Get details for a single campaign.' The word 'single' distinguishes it from list/report siblings such as get_campaign_performance, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus get_campaign_performance, get_account_hierarchy, or the mutation siblings. The read-only retrieval intent is only implied by the verb 'Get'.

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