Skip to main content
Glama

google_ads_callouts_remove

Unlink a callout asset from a Google Ads campaign to stop it from serving. The asset remains available for reattachment.

Instructions

Detach a callout asset from a Google Ads campaign by removing the CampaignAsset link. Returns {resource_name} of the removed campaign-asset association. Destructive — the callout stops serving on the campaign but the Asset row itself is not deleted. Re-enabling requires google_ads_callouts_create with the same text. For the sibling list operation use google_ads_callouts_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYesAsset ID as a numeric string (e.g. '123456789'). Obtain from the 'id' field of google_ads_callouts_list.
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.
Behavior4/5

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

Given no annotations, the description covers key behavioral traits: destructive action, what is destroyed (link, not asset), return value, and re-enabling path. Lacks error case details but is adequate for this simple 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 concise sentences, front-loaded with purpose, then behavioral notes, then sibling reference. No wasted words.

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?

No output schema, but description specifies return value. Covers destructive nature, non-deletion of asset, and re-enabling. Missing error handling info, but for this tool's complexity it is sufficiently complete.

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%, and the description adds no new parameter information beyond what the schema provides. Baseline 3 is appropriate.

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 action (detach, remove), the resource (callout asset from campaign), and the return value. It also distinguishes from sibling tools like create and list.

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 explains when to use (to detach a callout), notes the destructive nature, and provides alternatives: re-enabling via create and listing via list.

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