Skip to main content
Glama

google_ads_sitelinks_remove

Detach a sitelink from a Google Ads campaign by removing the CampaignAsset link. Stops the asset from serving without deleting it; re-link using google_ads_sitelinks_create if needed.

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

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly says 'Destructive', explains that it only unlinks the asset without deleting the underlying Asset row, and notes the return value. This is highly transparent about consequences and side effects.

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?

The description is concise and front-loaded with the core purpose. Each sentence provides essential information: the operation, the return value, the destructive nature, and related actions. No fluff or repetition.

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 simple detach operation with no output schema, the description is complete. It covers the return value, side effects (does not delete the Asset row), and how to undo (re-link via create). It also tells users how to list existing sitelinks, providing full contextual coverage.

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?

The input schema has 100% coverage with detailed descriptions for all parameters, so the description does not need to add parameter semantics. It adds no additional parameter information, but the baseline of 3 is appropriate given the schema's thoroughness.

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's purpose: 'Detach a sitelink asset from a Google Ads campaign by removing the CampaignAsset link.' It uses a specific verb, names the resource, and distinguishes itself from sibling tools like google_ads_sitelinks_list and google_ads_sitelinks_create.

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 clear contextual guidance: it says re-linking requires google_ads_sitelinks_create and lists sitelinks via google_ads_sitelinks_list. It does not explicitly state when not to use this tool, but the destructive warning and alternatives make the intended usage clear.

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