Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft structured snippets

draft_structured_snippets

Create Google Ads structured snippet assets and preview their campaign link; nothing changes until the plan is confirmed.

Instructions

Draft campaign structured snippet assets — returns a PREVIEW.

Creates structured snippet assets and links them to the campaign. Returns a preview with a plan_id; 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
snippetsYesAt least one dict with "header" and "values". header is one of Amenities, Brands, Courses, Degree programs, Destinations, Featured Hotels, Insurance coverage, Models, Neighborhoods, Services, Shows, Styles, Types (exact spelling). values is a list of 3-10 non-empty strings, each at most 25 characters.
campaign_idYesNumeric ID of the campaign to attach the snippets to.
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.

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 / campaign_id / description
      Added value: +"Numeric ID of the campaign to attach the snippets to."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / snippets / description
      Added value: +"At least one dict with \"header\" and \"values\". header is one of\nAmenities, Brands, Courses, Degree programs, Destinations, Featured\nHotels, Insurance coverage, Models, Neighborhoods, Services, Shows,\nStyles, Types (exact spelling). values is a list of 3-10 non-empty\nstrings, each at most 25 characters."
  2. First observedv0.9.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only give the generic safety flags (readOnlyHint=false, destructiveHint=false, openWorldHint=true); the description adds the non-obvious commit model — returns a plan_id preview and nothing changes until confirm_and_apply. That is genuine behavioral context beyond the structured fields, though it omits auth/permission requirements.

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?

Two short paragraphs, front-loaded with the purpose and the PREVIEW behavior. The trailing Google Ads API documentation link is mildly filler and doesn't earn as much space as the rest, but overall it is tight.

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?

With an output schema present and 100% schema coverage, the description need not restate return fields; it still usefully names plan_id. Annotations cover the safety profile and the description covers the draft/apply workflow, leaving nothing an agent needs 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%, so the schema already documents campaign_id, customer_id, and the header/values constraints of snippets. The description adds no parameter detail over the schema, 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 ('Draft campaign structured snippet assets') plus a scope qualifier ('returns a PREVIEW'). The resource name itself distinguishes it from sibling asset drafts like draft_callouts, draft_sitelinks, and draft_image_assets, so an agent can select it without opening the schema.

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?

Clearly frames the two-phase workflow by naming confirm_and_apply as the step that actually applies changes, which tells the agent when this tool fits. It stops short of explicitly excluding alternatives (e.g., when to prefer a direct update over drafting), so it is clear context without exclusions.

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