Metadata MCP Connector

Create Microsoft Ads Structured Snippet Extension

create_microsoft_structured_snippet_extension

Add a labeled list of offerings (structured snippet) shown beneath a Microsoft Ads (Bing) 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, microsoft ads, bing, extension

            WHEN TO USE:
            - "Add a structured snippet listing our service tiers on Microsoft Ads"
            - "Create a Bing snippet under 'Brands' with Nest, Nexus, Chromebook"
            - "Register a list of supported integrations as a Microsoft Ads snippet extension"

            WHEN NOT TO USE:
            - Want a single phrase (e.g. "Free Shipping") → use create_microsoft_callout_extension
            - Want clickable links to subpages → use create_microsoft_sitelink_extension
            - Want a pricing table (with amounts) → use create_microsoft_price_extension
            - Same snippet for Google Ads → use create_google_structured_snippet_extension

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

            EXAMPLE:
            create_microsoft_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.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, covering the safety profile. The description adds context about the creation action and the resulting structure (header plus 3-10 values), plus the note that Microsoft Ads mirrors Google's header vocabulary. It does not mention side effects like requiring an existing account or campaign, but for a create operation this is not a significant gap given the annotations.

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?

The description is well-structured with sections (purpose, keywords, when to use, when not, inputs, example) and is front-loaded with the core purpose. While the 'KEYWORDS' section adds some redundancy, the overall organization makes it easy to scan, and every other section earns its place, especially the disambiguation guidance. It is longer than minimal but justified by the need to differentiate among many sibling tools.

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 simple two-parameter create tool, the description is remarkably complete. It covers what the tool does, when to use it, when not to use it (with explicit alternatives), parameter semantics with an example call, and even hints at the header vocabulary. Since there is no output schema, the description doesn't need to explain return values. An agent has all the information needed to call this tool correctly.

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

Parameters4/5

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

The input schema already describes both parameters with lengths and basic descriptions (100% coverage), so baseline is 3. The description adds value by providing example values ('Brands' with 'Nest', 'Nexus', 'Chromebook'), explaining the header vocabulary mirroring Google's predefined list, and clarifying that values are short items. This goes beyond the schema's minimal constraints.

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 tool's purpose: 'Add a labeled list of offerings (structured snippet) shown beneath a Microsoft Ads (Bing) ad'. It also provides concrete examples of headers and values, and explicitly differentiates from sibling tools in the 'WHEN NOT TO USE' section, naming alternatives like callout, sitelink, price, and Google snippet extensions.

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 includes dedicated 'WHEN TO USE' and 'WHEN NOT TO USE' sections. It lists example user requests that should trigger this tool, and explicitly routes to alternative tools for other scenarios, e.g., 'Want a single phrase → use create_microsoft_callout_extension' and 'Same snippet for Google Ads → use create_google_structured_snippet_extension'. This is exactly what an agent needs to select the correct tool.

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?