Skip to main content
Glama

google_ads_sitelinks_remove

Unlink a sitelink asset from a Google Ads campaign to stop it from serving. The underlying asset is not deleted.

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, scope (unlinks but does not delete Asset row), and return value. With no annotations, the description carries the burden and covers key behavioral traits, though could mention idempotency or error conditions.

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?

Five sentences, each earning its place: purpose, return, scope clarification, re-linking guidance, list alternative. Front-loaded and no wasted words.

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 removal tool with full schema coverage and no output schema, the description covers purpose, behaviour, parameters, and sibling relationships completely.

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 coverage is 100%. Description adds value beyond schema: customer_id fallback to credentials, campaign_id source via campaigns_list, asset_id source from sitelinks_list with level constraint.

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 verb 'Detach' and resource 'sitelink asset from a Google Ads campaign'. It distinguishes from siblings by noting it does not delete the underlying Asset row and pointing to list and create tools.

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?

Explicitly says 'Destructive — unlinks the asset from the campaign so it stops serving' and provides alternative: 'Re-linking requires google_ads_sitelinks_create' and 'To list current sitelinks use google_ads_sitelinks_list'. Gives clear when-to-use and when-not-to-use guidance.

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