Metadata MCP Connector

List Search Ad Extensions

list_extensions

Read-only

List the account's Google Ads / Microsoft Ads library extensions (sitelinks, callouts, snippets, etc.) with their internal ids.

            ALSO KNOWN AS: list extensions, show extensions, find sitelink, which extensions do we have, extension library, browse extensions

            KEYWORDS: list, show, find, browse, extensions, sitelink, callout, library, google ads, microsoft ads, bing, id

            WHEN TO USE:
            - "What sitelinks do we have?" / "Show our Google Ads extensions"
            - ALWAYS before add_extensions_to_native_campaign or remove_extensions_from_native_campaign — those need internal ids, and this is the only tool that returns them. The create_*_extension tools return an empty body and cannot tell you the new id.

            WHEN NOT TO USE:
            - Creating a new extension → use the relevant create_*_extension tool
            - Non-search channels (Facebook / LinkedIn / Reddit) — extensions do not exist there

            INPUTS:
            - channel (required): GOOGLE_ADS or MICROSOFT_ADS
            - types (optional):   filter, e.g. ["SITELINK"]
            - name (optional):    name filter. Extension names are AUTO-DERIVED, not user-chosen — a sitelink's name is its link text and both description lines joined by newlines, truncated to 50 chars. Filter by `types` and match on the returned fields instead of guessing a name.
            - page / size (optional): pagination, defaults 0 / 50

            Returns {totalElements, totalPages, data:[{id, name, type, createdDate, ...}]}. Only campaign-attachable extensions are listed (account-level ones are excluded by the platform).

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Optional name filter. Names are auto-derived by the platform, not user-chosen, so prefer filtering by `types`.
`page`	No	0-based page index. Defaults to 0.
`size`	No	Page size. Defaults to 50.
`types`	No	Optional extension-type filter, e.g. ["SITELINK"].
`channel`	Yes	Search channel. Ad extensions are a search-channel-only concept.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial behavior: it returns only campaign-attachable extensions, excludes account-level ones, explains auto-derived names, and discloses pagination defaults. It also warns that create_*_extension tools return an empty body and cannot supply the new id.

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 long but every section earns its place: aliases, keywords, explicit when-to-use, parameter guidance, and return shape. The structure is scannable and front-loaded with the core purpose before details.

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?

The tool has no output schema, but the description supplies the return shape ({totalElements, totalPages, data}) and critical caveats about account-level extensions being excluded. Combined with the parameter guidance and sibling routing, an agent has everything needed to invoke it correctly.

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?

Although schema coverage is 100%, the description adds meaningful semantics beyond the schema: it clarifies that names are auto-derived and should not be guessed, recommends filtering by `types`, and documents pagination defaults. This directly prevents a common misuse of the name parameter.

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 identifies the action ('List'), the resource ('Google Ads / Microsoft Ads library extensions'), and the specific deliverable ('internal ids'). It distinguishes itself from the many create_*_extension tools and add_extensions_to_native_campaign / remove_extensions_from_native_campaign siblings by stating this is the only tool that returns ids.

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?

Explicit 'WHEN TO USE' and 'WHEN NOT TO USE' sections give concrete invocation triggers and exclusions. It names the alternatives (create_*_extension for new extensions) and states that extensions do not exist on non-search channels.

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

All Metadata MCP Connector tools Inspect

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

Need Help?