Skip to main content
Glama

Metadata MCP Connector

by io.metadata.mcp-server
OverviewDiscussionsAdmin

Create Google Ads Sitelink Extension

create_google_sitelink_extension

Add an extra clickable shortcut (sitelink) that appears beneath a Google Ads ad — helpful deep-links like "See Pricing", "Book a Demo", or "Contact Sales" with two short description lines. Sitelinks lift click-through rate by giving searchers alternate landing paths to the same advertiser.

            ALSO KNOWN AS: sitelink, site link, extra link, ad link, secondary link, deep link, additional link, jump link

            KEYWORDS: sitelink, site link, link, deep link, shortcut, google ads, extension, pricing link, demo link, contact link, landing page, CTR, click through

            WHEN TO USE:
            - "Add a sitelink to our Google Ads library"
            - "Create a 'See Pricing' / 'Book a Demo' / 'Contact Sales' link extension"
            - "Register a new sitelink for the homepage redesign"
            - "I need a shortcut under our search ads that points to the new pricing page"

            WHEN NOT TO USE:
            - Want a non-clickable selling-point snippet ("Free Shipping", "24/7 Support") → use create_google_callout_extension
            - Want a labeled list of offerings (e.g. "Brands: Nest, Nexus") → use create_google_structured_snippet_extension
            - Same sitelink for Microsoft Ads / Bing → use create_microsoft_sitelink_extension (library entries are per-channel)
            - Anything for Facebook / LinkedIn / Reddit — ad extensions are a search-channel-only concept

            INPUTS (all required):
            - url:          destination the sitelink opens.
            - link_text:    visible link text (1-25 chars).
            - description1: first description line under the link (1-35 chars).
            - description2: second description line (1-35 chars).

            EXAMPLE:
            create_google_sitelink_extension(
                url="https://example.com/pricing",
                link_text="See Pricing",
                description1="Plans for every team size",
                description2="Start free, upgrade anytime",
            )

            Returns the persisted extension (id, externalId, type=SITELINK, channel=GOOGLE_ADS). A 400 usually means a character-limit was exceeded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesDestination URL the sitelink points to (non-blank).
link_textYesVisible link text. 1-25 characters.
description1YesFirst description line. 1-35 characters.
description2YesSecond description line. 1-35 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only state that the operation is not read-only and not destructive; the description adds significant behavioral context by describing the returned persisted extension (id, externalId, type, channel), typical error behavior for character-limit violations, and the fact that the extension lands under the ad. There is no contradiction between the 'create' semantics and 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 clear headers, a concrete example, and a front-loaded definition, but the 'ALSO KNOWN AS' and 'KEYWORDS' lists contain many redundant synonyms that add bulk without meaningful selection value. It is organized enough to scan quickly while still carrying some fluff.

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?

Despite having no output schema, the description discloses the return shape and a common error cause, and it provides all required inputs, a working example, and clear routing to sibling tools. For a four-parameter creation tool, this is complete enough 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.

Parameters4/5

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

The input schema already covers all four parameters with character limits and non-blank constraints, so the baseline is 3. The description adds a complete invocation example and clarifies each parameter's real-world role (e.g., 'visible link text' and 'first description line'), which goes slightly beyond the schema's basic wording. This is useful but somewhat redundant with the schema, hence a 4.

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 identifies a specific verb ('Add'), a concrete resource ('extra clickable shortcut / sitelink beneath a Google Ads ad'), and distinguishes it from sibling extension tools by naming what it is not (callouts, structured snippets, Microsoft sitelinks). It also includes examples of link text and landing paths, leaving no ambiguity about what the tool creates.

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?

It contains an explicit WHEN TO USE section with example user requests, and a detailed WHEN NOT TO USE section listing the exact alternative tools for non-clickable snippets, structured snippets, and Microsoft Ads. This directly guides an agent to the correct sibling 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 toolsInspect
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