Skip to main content
Glama

google_ads_sitelinks_remove

Detach a sitelink asset from a Google Ads campaign to stop it from serving. The underlying asset remains and can be re-linked later.

Instructions

Detach a sitelink asset from a Google Ads campaign by removing the CampaignAsset link. Returns {resource_name} of the removed campaign-asset association. Destructive — unlinks the asset from the campaign so it stops serving, but does not delete the underlying Asset row. Re-linking requires google_ads_sitelinks_create with the same text/URL. To list current sitelinks use google_ads_sitelinks_list.

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.
asset_idYesAsset ID as a numeric string (e.g. '123456789'). Obtain from the 'id' field of google_ads_sitelinks_list rows where level=='campaign'.
Behavior4/5

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

Discloses destructive nature (unlinks, stops serving), non-deletion of asset, and return value (resource_name). Lacks details on error handling or prerequisites, but with no annotations, it provides sufficient transparency for a removal operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences: main action, behavioral note, and usage guidance. No redundancy, efficient structure.

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?

Covers main behavior, return value, and parameter sourcing. Lacks output schema but mentions return value. Could include error cases, but overall complete for detach operation.

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

Parameters4/5

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

Schema coverage is 100%, and description adds value by explaining optional fallback for customer_id, and how to obtain campaign_id and asset_id from other tools. This goes beyond the schema descriptions.

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 detaches a sitelink asset from a campaign by removing the CampaignAsset link, distinguishing it from deletion of the asset itself. The verb 'detach' is specific and differentiates from sibling tools like google_ads_callouts_remove.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use (detach sitelink), what not to do (does not delete asset), and alternatives: re-linking via google_ads_sitelinks_create and listing via google_ads_sitelinks_list. Also provides how to obtain IDs from other tools.

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