Metadata MCP Connector

Create Google Ads Structured Snippet Extension

create_google_structured_snippet_extension

Add a labeled list of offerings (structured snippet) shown beneath a Google Ads ad — a category header plus 3-10 short items, e.g. header "Brands" with values "Nest", "Nexus", "Chromebook", or header "Services" with "Hosting", "DNS", "CDN". Helps searchers self-qualify before clicking.

            ALSO KNOWN AS: structured snippet, snippet, category list, offering list, header values, product list, service list

            KEYWORDS: structured snippet, snippet, header, values, brands, services, products, courses, destinations, list, category, google ads, extension

            WHEN TO USE:
            - "Add a structured snippet listing our service tiers"
            - "Create a snippet under 'Brands' with Nest, Nexus, Chromebook"
            - "Register a list of supported integrations as a snippet extension"
            - "Show our product categories below our Google Ads"

            WHEN NOT TO USE:
            - Want a single phrase (e.g. "Free Shipping") → use create_google_callout_extension
            - Want clickable links to subpages → use create_google_sitelink_extension
            - Want a pricing table (with amounts) → use create_google_price_extension
            - Same snippet for Microsoft Ads / Bing → use create_microsoft_structured_snippet_extension

            INPUTS:
            - header: snippet category title (1-25 chars). The Google-Ads vocabulary requires picking one of Google's predefined header names ("Brands", "Models", "Service catalog", "Insurance coverage", etc.) — pass the chosen header string here.
            - values: 3-10 items, each 1-25 chars.

            EXAMPLE:
            create_google_structured_snippet_extension(
                header="Brands",
                values=["Nest", "Nexus", "Chromebook"],
            )

Input Schema

TableJSON Schema

Name	Required	Description	Default
`header`	Yes	Snippet header. 1-25 characters.
`values`	Yes	3-10 snippet values, each 1-25 characters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating a non-read, non-destructive operation, which aligns with the 'Add' action. The description adds useful context about the structure (header + 3-10 values) and the Google predefined header vocabulary, but does not explicitly state side effects (e.g., extension appears immediately) or permission requirements. It does not contradict the annotations, and adds moderate value beyond them.

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 well-structured with clear sections (ALSO KNOWN AS, KEYWORDS, WHEN TO USE, WHEN NOT TO USE, INPUTS, EXAMPLE). Each section earns its place and the main purpose is front-loaded. It is comprehensive without being redundant.

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 two-parameter create tool with no output schema, the description is complete: it explains what the tool does, when to use it, when not to use it, the exact parameter constraints (including the predefined header vocabulary), and provides a full example call. Nothing essential is missing for an agent 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 the schema describes both parameters at 100% coverage, the description adds critical semantic value: it explains that the header must be one of Google's predefined names and provides example values. This is beyond the schema's simple maxLength/minLength constraints and materially improves parameter understanding.

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 verb ('Add') and the resource ('labeled list of offerings (structured snippet) shown beneath a Google Ads ad'), and gives concrete examples (header 'Brands' with values). It also explicitly differentiates from sibling tools in the 'WHEN NOT TO USE' section, so an agent can distinguish it from create_google_callout_extension, create_google_sitelink_extension, etc.

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?

The description provides explicit 'WHEN TO USE' and 'WHEN NOT TO USE' sections with specific example queries and names the exact alternative tools (callout, sitelink, price, Microsoft snippet). This gives clear routing guidance with no ambiguity.

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?