Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft pausing an entity

pause_entity

Pause a Google Ads campaign, ad group, ad, or keyword by generating a preview plan; apply it later to make the change. Pausing is reversible.

Instructions

Draft pausing a campaign, ad group, ad, or keyword — returns a PREVIEW.

Pausing is reversible with enable_entity. Returns a preview with a plan_id (target status PAUSED); nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_idYesID in the format for its type. campaign: campaign ID (e.g. "12345678"); ad_group: ad group ID (e.g. "12345678"); ad: "adGroupId~adId" (e.g. "12345678~987654"; a bare ad ID is resolved to its ad group at apply time); keyword: "adGroupId~criterionId" (e.g. "12345678~987654").
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
entity_typeYes"campaign", "ad_group", "ad", "keyword" or "asset_group" (Performance Max).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / entity_id / description
      Added value: +"ID in the format for its type. campaign: campaign ID (e.g.\n\"12345678\"); ad_group: ad group ID (e.g. \"12345678\"); ad:\n\"adGroupId~adId\" (e.g. \"12345678~987654\"; a bare ad ID is resolved\nto its ad group at apply time); keyword: \"adGroupId~criterionId\"\n(e.g. \"12345678~987654\")."
    • addedInput schema / properties / entity_type / description
      Added value: +"\"campaign\", \"ad_group\", \"ad\", \"keyword\" or\n\"asset_group\" (Performance Max)."
  2. First observedv0.9.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses that the call returns a PREVIEW with a plan_id and a target status of PAUSED, that no changes happen until confirm_and_apply is used, and that the action is reversible. This is exactly the behavioral context an agent needs for a draft/pending mutation tool.

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 front-loaded with the core action and preview behavior, then follows with the reversibility/apply workflow, then a reference link. Every sentence earns its place; 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?

Given the output schema, annotations, and 100% schema coverage, the description supplies the remaining critical context: that this is a preview-only draft operation, how it relates to confirm_and_apply and enable_entity, and the target status. An agent has enough to invoke it correctly.

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%, so the input schema already fully documents entity_id formats, customer_id defaulting, and entity_type values. The description repeats the entity types in prose but adds no parameter-level syntax or constraints beyond the schema, so 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?

The description gives a specific verb+resource: 'Draft pausing a campaign, ad group, ad, or keyword — returns a PREVIEW.' It cleanly distinguishes the tool from direct mutations by emphasizing that it only produces a preview, and it names the follow-up tool (confirm_and_apply) and the reverse action (enable_entity).

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?

It clearly situates the tool in a two-step workflow: nothing changes until confirm_and_apply applies the preview, and pausing is reversible with enable_entity. It doesn't spell out exclusions (e.g., when to use pause_reddit_entity or a direct update instead), but the context for use is unambiguous.

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