Skip to main content
Glama

google_ads_sitelinks_create

Create and link a sitelink asset to a Google Ads campaign. Validates the 20-sitelink limit and returns the resource name on success.

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
final_urlYesAbsolute landing URL (http:// or https://) for the sitelink. Must be a crawlable page on the advertiser's verified domain.
link_textYesLink text shown to searchers (e.g. 'Pricing'). Google Ads limits this to 25 characters.
campaign_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
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.
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.
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses the two-step mutate, return values on success and failure, the hardcoded max limit (20), the non-removable nature (only reversible by remove), and that each call creates a new asset (duplicates possible). It does not mention permission requirements or rate limits, but otherwise is transparent.

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 four sentences and includes both behavioral and usage information. It is fairly concise but could be slightly more structured (e.g., separating purpose from details). It avoids verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters (3 required), no output schema, and no annotations, the description covers the key aspects: creation process, return values, error conditions, and relation to sibling tools. It is sufficient for an agent to understand and use the tool 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 baseline is 3. The description adds minimal extra meaning beyond the schema; it only mentions the max length for link_text and the dependency between description1 and description2 implicitly. The schema already describes each param adequately.

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 the tool creates a sitelink asset and links it to a campaign via a two-step mutate. It distinguishes from siblings by referencing google_ads_sitelinks_remove for reversibility, and the name itself contrasts with list/remove tools.

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 provides context on when to use (creating a sitelink asset) and mentions the max limit of 20 campaign-level sitelinks and duplicate asset creation. However, it does not explicitly state when not to use or compare to alternatives beyond remove.

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