Metadata MCP Connector

Create Google Ads Business Logo Extension (BETA)

create_google_business_logo_extension

Attach the business logo to a Google Ads text ad for brand recognition. BETA. References a single image-library asset (the logo) and optionally pairs it with the business name and domain (the latter two are also used when the same logo is reused for Microsoft Ads).

            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, google ads, extension

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

            WHEN NOT TO USE:
            - Multiple product / lifestyle shots → use create_google_image_extension
            - The logo is not yet in the image library — upload it first, then call this with the resulting ID.
            - Same logo for Microsoft Ads / Bing → use create_microsoft_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). Required if the same library entry is also used for Microsoft Ads.
            - domain_name:     business domain (≤50 chars). Used by Microsoft Ads.

            EXAMPLE:
            create_google_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 already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this is a non-destructive creation operation. The description adds valuable context beyond annotations: the BETA status, that it references a single image-library asset, and that business_name/domain_name are reused for Microsoft Ads. It does not contradict annotations and enriches the behavioral profile.

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 longer than minimal but well-organized with clear section headers (WHEN TO USE, WHEN NOT TO USE, INPUTS, EXAMPLE). The core purpose is front-loaded, and the additional sections each add functional value. The 'ALSO KNOWN AS' and 'KEYWORDS' sections are somewhat redundant for agent use but do not harm clarity.

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 tool with 3 parameters, no output schema, and cross-platform implications (Microsoft Ads), the description covers prerequisites, exclusions, parameter semantics, and a worked example. Nothing essential for correct invocation is missing; the only potential gap is error handling or return behavior, but that is not specified in any schema and is reasonably omitted given the straightforward creation action.

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 full responsibility for explaining parameters. The INPUTS section defines each parameter's meaning, constraints (≤25 chars, ≤50 chars), and the conditional requirement for business_name when reusing the asset for Microsoft Ads. This goes well beyond the schema's type and maxLength, fully compensating for the zero schema coverage.

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 attaches a business logo to a Google Ads text ad, with the specific verb 'attach' and resource 'business logo extension'. It differentiates from siblings by explicitly naming create_google_image_extension and create_microsoft_business_logo_extension in the WHEN NOT TO USE section, so an agent can disambiguate without opening their schemas.

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 WHEN TO USE and WHEN NOT TO USE sections provide explicit guidance: examples of natural-language triggers, exclusions for product/lifestyle images and Microsoft Ads, and a prerequisite (upload logo first). This leaves no ambiguity about when to invoke this tool versus alternatives.

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?