AdCopilot

Google Ads: create sitelink asset

create_sitelink_asset

Creates a sitelink asset that can be linked to campaigns or ad groups.

Creating it changes no ad: it shows only once linked with
link_asset_to_campaign, link_asset_to_ad_group or
link_assets_to_customer.

Sitelinks add additional links below your ad, directing users to specific pages.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    link_text: The text displayed for the sitelink (max 25 characters).
    final_url: The URL the sitelink directs to.
    description1: First line of description (max 35 characters). Optional.
    description2: Second line of description (max 35 characters). Optional.
    start_date: Start date in YYYY-MM-DD format. Optional.
    end_date: End date in YYYY-MM-DD format. Optional.

Returns:
    Dictionary with the created asset resource name.

Tools revision: d80f65c0.

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>",
      "link_text": "<link_text>",
      "final_url": "<final_url>"
    },
    "name": "create_sitelink_asset"
  }
}

Input Schema

Name	Required	Description	Default
`end_date`	No
`final_url`	Yes
`link_text`	Yes
`start_date`	No
`customer_id`	Yes
`description1`	No
`description2`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false), so the bar is lower. The description adds real behavioral context: creating the asset has no effect on any ad until it is linked, which prevents an agent from assuming immediate impact. It does not discuss duplicate handling or validation failures, which the non-idempotent hint implies but does not explain.

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?

Front-loaded with the action and the critical 'nothing happens until linked' caveat, then structured Args/Returns sections that are easy to scan. The explanatory line about what sitelinks do is slightly redundant with the opening sentence but is short and adds domain context for the char-limited description fields.

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?

For a seven-parameter creation tool with an output schema, the definition covers action, non-effect until linking, per-parameter formats and limits, and return shape ('asset resource name'). An agent has everything needed to call it correctly and to know what to do next.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does so: it documents all seven parameters, marks which are optional, gives character limits (25 for link_text, 35 per description line), the date format YYYY-MM-DD, and the 'numbers only, no hyphens' constraint on customer_id. This is meaning the schema does not supply.

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?

Uses a specific verb and resource ('Creates a sitelink asset') and immediately clarifies scope: it creates the asset only, and it 'shows only once linked.' That distinguishes it from the link_* siblings and from the other create_*_asset tools that each produce a different asset type.

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?

Explicitly states the follow-up requirement and names the three linking alternatives (link_asset_to_campaign, link_asset_to_ad_group, link_assets_to_customer), which is genuinely useful routing guidance. It does not say when to prefer a sitelink over a callout, snippet, or price asset, so sibling asset-type selection is inferred from the asset name rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?