Skip to main content
Glama

AdCopilot

by cloud.adcopilot.mcp
OverviewDiscussionsAdmin

Google Ads: list asset links

list_asset_links
Read-onlyIdempotent

Lists every asset link in an account — account, campaign and ad group.

One call answers "which phone numbers, sitelinks, callouts... are on, and
where?": each link comes back with its level, field type, status (what
the advertiser set: ENABLED or PAUSED), primary status (whether Google is
actually serving it), the asset's ID, type and text, the campaign / ad
group it sits on, and the tool and arguments that pause or re-enable it.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    field_type: Only links of this field type, e.g. CALL. Optional.
    include_removed: Also return REMOVED links (deleted earlier, e.g. in
        the Google Ads UI; they no longer serve and cannot be changed
        here). Defaults to False.

Returns:
    Dictionary with the links, and counts of links by status.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
field_typeNo
customer_idYes
include_removedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context beyond them: the distinction between advertiser-set status and Google's primary status, and the fact that REMOVED links no longer serve and cannot be changed here. That is exactly the kind of behavioral nuance annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line scope statement, then the useful payload summary, then per-arg notes. It is on the longer side and the Args/Returns block partly restates the schema structure, but each clause carries information an agent needs.

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 read-only list tool with an output schema and three parameters, the description covers scope, return contents, status semantics, and edge cases (removed links). Nothing an agent needs to call it correctly is missing.

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 0%, so the description must carry the load and does: customer_id format (numbers only, no hyphens), field_type semantics with an example (CALL), and include_removed semantics including why a removed link matters. All three parameters gain meaning beyond the bare schema.

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?

Opens with a specific verb+resource+scope: 'Lists every asset link in an account — account, campaign and ad group.' The scope statement distinguishes it from the write-side siblings (link_asset_to_campaign, set_campaign_asset_status), so an agent can tell what it does without opening the schema.

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?

Gives a concrete usage framing ('One call answers which phone numbers, sitelinks, callouts... are on, and where?') and implies the pause/re-enable path by returning 'the tool and arguments that pause or re-enable it.' It stops short of naming a specific sibling alternative or stating when not to use it, so it is clear context rather than explicit routing.

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

All AdCopilot 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