Skip to main content
Glama
Sign In

Google Ads

by io.github.mcp-dir
OverviewDiscussionsAdmin

google_ads_sitelink_remove

Detach sitelinks from a campaign / account / ad group. Pass the link_resource_name(s) from google_ads_sitelinks. Removes only the association (the shared sitelink asset stays in the account library), so it is reversible by re-attaching.

Bulk support: accepts customer_ids for batched execution.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "link_resource_names": "<link_resource_names>"
    },
    "name": "google_ads_sitelink_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
customer_idNo
customer_idsNo
partial_failureNo
link_resource_namesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description explicitly states that only the association is removed, the asset remains in the library, and the operation is reversible. This directly addresses the side effects and aligns with the destructiveHint=false annotation, providing clear transparency about the impact.

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, two sentences, with the main purpose front-loaded and additional details (reversibility, bulk support) neatly appended. No unnecessary elaboration.

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 the lack of output schema and 5 parameters, the description provides sufficient context for the core functionality and key parameter usage. It does not explain return values or error handling, but for a mutation tool with reversible effects, the provided context is adequate.

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 description explains link_resource_names (source) and customer_ids (bulk usage), but does not elaborate on account, customer_id, or partial_failure. Since schema descriptions are absent, the description only partially compensates for parameter meaning; some parameters remain ambiguous.

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 sitelinks) and the target resources (campaign/account/ad group). It distinguishes from related tools like google_ads_sitelink_create and google_ads_sitelinks by specifying removal and the source of link_resource_names.

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?

It explains when to use the tool (to detach sitelinks), how to obtain the required link_resource_names (from google_ads_sitelinks), and mentions bulk support via customer_ids. However, it does not explicitly state when not to use it or mention alternative tools for deletion of assets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Google Ads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources