Skip to main content
Glama

google_ads_sitelinks_create

Create a sitelink asset and attach it to a Google Ads campaign, with a hard limit of 20 sitelinks per campaign.

Instructions

Create a sitelink Asset and link it to a Google Ads campaign in a two-step mutate (AssetService then CampaignAssetService). Returns {resource_name} of the created asset on success, or {error:true, error_type:'validation_error', message} when the campaign already has 20 campaign-level sitelinks (hardcoded _MAX_SITELINKS_PER_CAMPAIGN limit). Mutating — reversible only by google_ads_sitelinks_remove using the returned asset_id. The asset is newly minted per call; identical text produces duplicate assets unless deduplicated upstream.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
link_textYesLink text shown to searchers (e.g. 'Pricing'). Google Ads limits this to 25 characters.
final_urlYesAbsolute landing URL (http:// or https://) for the sitelink. Must be a crawlable page on the advertiser's verified domain.
description1NoOptional first description line (max 35 characters). Only displayed when description2 is also provided and Google chooses to render the expanded format.
description2NoOptional second description line (max 35 characters). Requires description1.
Behavior5/5

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

With no annotations, the description fully discloses the two-step mutation, the hardcoded limit, reversible nature, and duplicate creation. It also specifies the output format on success and error. No contradictions.

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?

The description is a single dense paragraph, front-loaded with the main action. It could be structured with bullet points, but no unnecessary information is present. It is concise and informative.

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 complex tool with two-step mutate, limit, duplicate handling, and no output schema, the description covers all essential behaviors: process, error case, reversibility, and duplicate creation. It is complete enough for an agent to use 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 coverage is 100%, so baseline is 3. The description does not add additional meaning to parameters beyond the schema descriptions. It mentions the limit and duplicate behavior but not parameter-specific details.

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 clearly states that the tool creates a sitelink asset and links it to a campaign via a two-step mutate. It distinguishes from sibling tools like google_ads_sitelinks_list and google_ads_sitelinks_remove by specifying the creation action and noting reversibility via remove.

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?

The description explains the two-step process, the 20-sitelink limit, and duplicate behavior, providing context for when to use. It does not explicitly state alternatives but mentions the remove tool for reversibility. This is clear but could be more direct.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server