Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft sitelinks

draft_sitelinks

Draft sitelink extensions for a campaign and preview them before applying. Validates each destination URL, blocks unreachable links, and returns a plan_id for confirmation.

Instructions

Draft sitelink extensions for a campaign — returns a PREVIEW.

Sitelinks appear as additional links below your ad, increasing click area and directing users to specific pages. Every final_url is fetched and an unreachable URL (HTTP 4xx/5xx) blocks the draft. Google recommends at least 4 sitelinks per campaign; fewer than 2 may not show. Returns a preview with a plan_id and any warnings; 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
sitelinksYesList of dicts (at least one), each with link_text (str, required, max 25 chars) — the clickable text shown; final_url (str, required) — destination URL for this sitelink; description1 (str, optional, max 35 chars) — first description line; description2 (str, optional, max 35 chars) — second description line.
campaign_idYesNumeric ID of the campaign to attach sitelinks 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 sitelinks to."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / sitelinks / description
      Added value: +"List of dicts (at least one), each with link_text (str,\nrequired, max 25 chars) — the clickable text shown; final_url (str,\nrequired) — destination URL for this sitelink; description1 (str,\noptional, max 35 chars) — first description line; description2\n(str, optional, max 35 chars) — second description line."
  2. First observedv0.9.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing that every final_url is fetched, that a 4xx/5xx response blocks the draft, Google's recommendation of at least 4 sitelinks, that fewer than 2 may not show, and that a plan_id plus warnings are returned with no side effects. This is exactly the kind of non-obvious behavioral detail an agent needs.

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?

Well front-loaded with the core purpose and preview semantics first, then supporting constraints. Slightly padded by the trailing Google Ads API documentation link, which adds little for tool selection.

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?

An output schema exists, so return values need not be re-explained, and the description still notes the preview shape (plan_id, warnings). Combined with the URL-validation behavior and the confirm_and_apply follow-up, an agent has everything needed to call 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 schema already documents campaign_id, sitelinks, and customer_id in detail, including char limits. The description adds no parameter-level syntax beyond the schema, so 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?

States a specific verb (draft), resource (sitelink extensions), and scope (for a campaign), plus the crucial qualifier that it returns a PREVIEW rather than applying changes. This distinguishes it cleanly from confirm_and_apply and from sibling drafters like draft_callouts.

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?

Explains the draft-then-confirm workflow ('nothing changes until confirm_and_apply applies it'), which tells the agent this is step one of two. It lacks explicit guidance on when to prefer sitelinks over other extension types, but the usage context is otherwise clear.

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