Metadata MCP Connector

Create Microsoft Ads Business Logo Extension (BETA)

create_microsoft_business_logo_extension

Attach the business logo to a Microsoft Ads (Bing) text ad for brand recognition. BETA. References a single image-library asset (the logo) and optionally pairs it with the business name and domain (which Bing surfaces alongside the logo on its SERP).

            ALSO KNOWN AS: business logo, brand logo, logo, company logo, brand mark, mark, identity asset

            KEYWORDS: logo, business logo, brand, brand mark, identity, company logo, brand recognition, BETA, microsoft ads, bing, extension

            WHEN TO USE:
            - "Add our business logo to our Microsoft Ads"
            - "Create a Bing logo extension referencing image library ID 123"
            - "Attach the Acme Corp logo to our Microsoft Ads search ads for brand lift"

            WHEN NOT TO USE:
            - Multiple product / lifestyle shots → use create_microsoft_image_extension
            - The logo is not yet in the image library — upload it first, then call this with the resulting ID.
            - Same logo for Google Ads → use create_google_business_logo_extension

            INPUTS:
            - image_library_id (required): single image library ID pointing to the logo asset.
            - business_name:   business name displayed alongside the logo (≤25 chars). Microsoft Ads surfaces this on the SERP.
            - domain_name:     business domain (≤50 chars). Microsoft Ads surfaces this on the SERP.

            EXAMPLE:
            create_microsoft_business_logo_extension(
                image_library_id=123,
                business_name="Acme Corp",
                domain_name="acme.com",
            )

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain_name`	No
`business_name`	No
`image_library_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations indicate this is not read-only and not destructive. The description adds useful behavioral context: it references a single existing image-library asset rather than uploading, optionally displays business name/domain on the SERP, and flags BETA status. No contradiction with 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 structure is well-organized with WHEN/INPUTS/EXAMPLE sections and front-loaded purpose. Some redundancy exists between the initial text and the repeated 'ALSO KNOWN AS' and 'KEYWORDS' sections, but overall every major section earns its place.

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 create-style tool with no output schema, the description covers prerequisites (logo must already be in image library), input semantics, an explicit example, and routing to alternatives. This is sufficient for correct invocation.

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 description coverage is 0%, so the description carries the full burden for parameters. It does so by explaining image_library_id points to the logo asset and clarifying the display behavior and character limits for business_name and domain_name, going beyond raw schema 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 states a specific verb ('Attach') and resource ('business logo' to a Microsoft Ads text ad) and explicitly differentiates itself from the image extension tool, so the agent can identify exactly what this tool does and how it differs from siblings.

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?

Provides concrete 'WHEN TO USE' examples and explicit 'WHEN NOT TO USE' cases, naming alternative tools such as create_microsoft_image_extension and create_google_business_logo_extension. This is clear routing guidance beyond what annotations offer.

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?