Metadata MCP Connector

Set Default Marketing Automation List

set_default_ma_list

Set the account's default marketing automation (MA) destination list.

                USAGE INSTRUCTIONS FOR LLM:
                WARNING: requires a concrete, resolved list_id. You MUST call search_ma_lists
                first and pass the exact "listId" of the match the user confirmed. Never invent
                or guess a list_id.

                The default is a SNAPSHOT source, not a live link: newly-created eligible campaign
                channels (not CTR goal, not Reddit) copy this value once at creation time. Setting
                a new default has no effect on channels already created, and duplicating a campaign
                always preserves the source channel's own value instead of consulting the default.

                WHEN TO USE THIS TOOL:
                - User wants to set or change the default marketing automation destination list
                - After search_ma_lists returns the list the user wants

                RESPONSE FORMAT:
                On success, returns the same shape as get_default_ma_list with status AVAILABLE.
                On failure, "status" is one of:
                - VALIDATION_FAILED: the list_id was not found in the connected MA tool
                - PERMISSION_DENIED: the caller lacks marketing-automation write access
                - DISCONNECTED: no marketing automation tool is connected to this account
                Each failure includes a "message" explaining why.

                EXAMPLE: "Set the default MA list to the one you just found" -> set_default_ma_list(list_id=12345)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`list_id`	Yes	A concrete list id already resolved via search_ma_lists. Never invent or guess one.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond the sparse annotations by disclosing that the default is a snapshot copied only at campaign creation, has no effect on already-created channels, and that duplication preserves the source channel's value. It also details failure statuses like VALIDATION_FAILED, PERMISSION_DENIED, and DISCONNECTED, which annotations do not cover. No contradiction exists with readOnlyHint=false or destructiveHint=false.

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 clearly structured with headings for usage instructions, behavior, when to use, response format, and an example, making it scannable. It is somewhat verbose and repeats the search_ma_lists prerequisite, but each section contributes useful information.

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 single-parameter mutation with no output schema, this description is effectively complete: it covers prerequisites, side-effect semantics, response/error shape, and provides a concrete example. An agent has enough context to call this tool correctly and to explain the outcome to a user.

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 documents list_id completely, and the description adds important operational meaning: the id must be a concrete, resolved value from search_ma_lists, never invented or guessed, and the example shows the expected argument. This elevates the parameter from a plain integer to a value with a required provenance.

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 names the exact action and resource: 'Set the account's default marketing automation (MA) destination list.' It is easily distinguishable from siblings like get_default_ma_list, clear_default_ma_list, and search_ma_lists, and the example reinforces the intended invocation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is an explicit 'WHEN TO USE THIS TOOL' section with concrete triggers, plus a mandatory prerequisite: call search_ma_lists first and pass the user-confirmed listId. It does not explicitly say when to use get_default_ma_list or clear_default_ma_list instead, so it stops short of full when-not guidance.

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?