Skip to main content
Glama

Honeyfield Marketing MCP

Google Ads: List campaigns

ads_list_campaigns
Read-only

Alle Kampagnen auflisten (Name, Status, Budget, Channel Type, Bidding Strategy). Enthält ENABLED und PAUSED; entfernte Kampagnen (REMOVED) sind ausgeblendet. Die ads_list_ad_groups/-ads/-keywords blenden Kinder entfernter Kampagnen ebenfalls aus, jede dort genannte campaign_id steht also auch hier. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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

Input Schema

NameRequiredDescriptionDefault
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description goes beyond that by disclosing the implicit status filter (REMOVED suppressed) and a cross-tool consistency guarantee with ads_list_ad_groups/ads_list_keywords/ads_list_ads. It says nothing about result volume, pagination, or cost/rate behavior for a live Google Ads API call, which is the remaining gap.

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?

Three sentences, front-loaded with the action and returned fields, then the status filtering rule, then the cross-tool consistency note, then the parameter. No sentence is redundant and no padding is present.

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?

An output schema exists, so return-value shape need not be explained; the description covers scope, filtering, cross-tool consistency and the only parameter. What remains unstated is whether results span all campaigns in the account/workspace on a single call or require paging — minor for a read-only list tool but relevant to agents planning a full inventory.

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?

Schema description coverage is 0%, so the description must carry the meaning of the single parameter — and it does: 'workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace)' explains both the value format (slug) and the optionality condition. That is meaningful compensation for the schema gap, though it does not explain resolution behavior when multiple workspaces exist.

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 (list all Google Ads campaigns) and immediately enumerates what comes back (name, status, budget, channel type, bidding strategy). It is clearly distinguishable from sibling list tools such as ads_list_ad_groups, ads_list_ads and ads_list_keywords because it explicitly defines the parent/child relationship between them.

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?

Gives concrete inclusion/exclusion rules: ENABLED and PAUSED are returned, REMOVED campaigns are hidden — exactly the question an agent asks before calling a list endpoint. It also explains how results line up with the child-list tools. It does not name alternatives (e.g. ads_campaign_performance for metrics, ads_list_experiments), so routing guidance is clear but not exhaustive.

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