Skip to main content
Glama
Sign In

Google Ads

by io.github.mcp-dir
OverviewDiscussionsAdmin

google_ads_sitelinks

Read-onlyIdempotent

List sitelink assets in the account and where they are attached (campaign / account / ad group level), with each link's resource_name (pass it to google_ads_sitelink_remove) and status. Use to audit existing sitelinks before creating new ones.

Bulk support: accepts customer_ids for batched execution.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "google_ads_sitelinks"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
customer_idNo
customer_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds behavioral detail beyond annotations: it lists the output fields (resource_name, status), attachment scoping, and bulk execution capability. It does not mention pagination or max batch size, but this is acceptable given annotation coverage.

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?

Two short paragraphs are well-structured and concise. The action is front-loaded, and each sentence provides meaningful information: listing behavior, output fields, use case, and bulk support. No redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is informative for a read-only list tool with good annotations: it covers output fields and usage intent. However, the ambiguity of account vs customer_id and the lack of any mention of pagination or result shape (with no output schema) leave some gaps. It is adequate but not fully complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only explains customer_ids ('Bulk support: accepts customer_ids for batched execution'). The distinction between account and customer_id is left unclear, and no other parameter guidance is provided. This is a significant gap for a 3-parameter tool.

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 it lists sitelink assets, their attachment levels, resource_name, and status. It distinguishes itself from sibling tools like google_ads_sitelink_create and google_ads_sitelink_remove by framing this as an audit/listing action.

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?

Explicit guidance is given: 'Use to audit existing sitelinks before creating new ones.' This indicates the intended context and separates it from creation/removal tools. It also notes bulk support via customer_ids, though it does not detail exclusions or alternative tools.

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