Skip to main content
Glama

Metadata MCP Connector

List Wizard Campaigns

list_wizard_campaigns
Read-only

List wizard (Metadata-native) campaigns for the current account with pagination, sorting, and experiment-status filtering.

            KEYWORDS: campaigns, list, browse, wizard, native, all campaigns, campaign list, launched campaigns, paused campaigns, active campaigns

            USE THIS TOOL WHEN THE USER ASKS:
            - "Show me all campaigns" / "List campaigns" / "What campaigns do we have?"
            - "Show active campaigns" / "List paused campaigns" / "Show completed campaigns"
            - "Show recent campaigns" / "Last N campaigns"
            - "Campaigns sorted by spend / leads / CPL / created date"
            - Page-by-page campaign browsing for the campaigns UI

            DO NOT USE if the user:
            - Wants details on ONE SPECIFIC campaign by name → use search_campaigns_by_names
            - Wants budget group info (not campaigns) → use list_budget_groups / get_budget_group
            - Wants per-experiment performance → use experiment_performance_stats / search_experiments

            TWO INDEPENDENT FILTERS (COMBINE TO MATCH UI TABS):

            1) status — filters by CAMPAIGN status. Accepts a comma-separated subset of: Draft, Launched, Finished.
               - Draft: the campaign exists but has never been launched.
               - Launched: the campaign has been launched (experiments may be Active, Paused, or idle).
               - Finished: the campaign has reached its end date.
               - Omit to include all three.

            2) experiment_statuses — filters by EXPERIMENT status inside each campaign. Accepts a comma-separated subset of:
               Active, WithoutSpend, Paused, Completed, Failed. Omit to include all five.

            HOW TO MIX THEM (mirrors the UI tabs on /campaigns):
            - "All" tab: omit both → API returns everything.
            - "Active" tab: status="Launched", experiment_statuses="Active,WithoutSpend" (launched campaigns with live or not-yet-spending experiments).
            - "Paused" tab: status="Launched", experiment_statuses="Paused" (launched campaigns whose experiments are paused).
            - "Draft" tab: status="Draft" (campaign hasn't been launched yet — experiment status doesn't apply).
            - "Finished" tab: status="Finished".

            SORTING:
            - sort_by: createdDate (default), startDate, endDate, name, budget, spent, leads, cpl, cpc, ctr, impressions, clicks, status
            - sort_order: asc | desc (default: desc)

            PAGINATION:
            - page: 0-based page index (default 0)
            - size: results per page (default 25; the UI campaign list fetches 25–50)

            RESPONSE SHAPE:
            {
              "totalElements": 435,
              "totalPages": 18,
              "data": [
                {
                  "id": 173290,
                  "accountId": 1455,
                  "name": "2026_Q2_NA_Builder_Content_...",
                  "createdDate": "2026-01-15T12:00:00Z",
                  "visibility": "VISIBLE" | "ARCHIVED",
                  "budget": 25,
                  "startDate": "...",
                  "endDate": "...",
                  "status": "Launched" | "Draft" | ...,
                  "activeExperiments": 9, "pausedExperiments": 0, "totalExperiments": 9,
                  "leads": 0, "spent": 0, "impressions": 48, "clicks": 0,
                  "cpc": 0, "cpl": 0, "ctr": 0.0,
                  "goal": "CTR" | "CPL",
                  "campaignGroup": "TOF - AO - Social - Billing - BA",
                  "tags": [...]
                }, ...
              ]
            }

            WORKFLOW (UI-style): list_wizard_campaigns(page=0, size=25) → render list → user clicks campaign → search_campaigns_by_names / get_campaign_by_wizard_id for details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional: server-side name substring filter.
pageNo0-based page index. Default: 0
sizeNoResults per page. Default: 25
statusNoCampaign-level status filter. Comma-separated subset of Draft, Launched, Finished. Omit to include all three. Combine with experiment_statuses to mirror the UI tabs (e.g. Active tab = status=Launched + experiment_statuses=Active,WithoutSpend).
sort_byNoField to sort by. Default: createdDate
sort_orderNoSort order. Default: desc
visibilityNoOptional: filter by campaign visibility. Omit to include all.
experiment_statusesNoExperiment-level status filter. Comma-separated subset of Active, WithoutSpend, Paused, Completed, Failed. Omit to include all five.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive; the description adds rich context beyond that: the semantic meaning of each status value (Draft = never launched, Launched = launched, Finished = end date), the independence of the two filters, pagination defaults (0-based page, size 25), and a full response-shape example. 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 description is long, but it is tightly structured with clear headers (KEYWORDS, USE WHEN, DO NOT USE, filters, SORTING, PAGINATION, RESPONSE SHAPE, WORKFLOW) and scannable bullets. Minor redundancy exists—the KEYWORDS section largely restates the intent examples—but overall each section earns its place given the tool has 8 parameters and no output schema.

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 supplies a complete response-shape example covering all returned fields, pagination envelope, and a workflow showing the UI-style call sequence and follow-up tools. For a complex 8-parameter listing tool with three enums, nothing an agent needs to select and invoke it correctly is missing.

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 coverage is 100%, so the baseline baseline is 3, but the description goes well beyond: it explains what each status value means, how status and experiment_statuses interact to mirror UI tabs, default values for sort_by/sort_order/page/size, and the full sortable field list. The description actually carries more parameter nuance than the schema's own descriptions.

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 opening sentence states a specific verb, resource, and scope: 'List wizard (Metadata-native) campaigns for the current account' with pagination, sorting, and experiment-status filtering. The 'DO NOT USE' section explicitly names sibling tools (search_campaigns_by_names, list_budget_groups, experiment_performance_stats) that handle different but related intents, so an agent can distinguish this tool without opening 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?

Provides explicit trigger phrases ('Show me all campaigns', 'Show active campaigns', 'Campaigns sorted by spend') and a 'DO NOT USE' section that routes specific intents to named alternatives. The UI-tab mapping (All/Active/Paused/Draft/Finished) further tells the agent exactly which parameter combinations to choose for each user request.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources