Metadata MCP Connector

Get Default Marketing Automation List

get_default_ma_list

Read-only

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

                USAGE INSTRUCTIONS FOR LLM:
                Use this to check whether the account has a default MA destination list configured,
                and its current health. Newly-created eligible campaign channels (not CTR goal,
                not Reddit) snapshot this value ONCE at creation time — it is not a live reference,
                so a later change here never retroactively updates channels already created.

                WHEN TO USE THIS TOOL:
                - User asks "what's our default marketing automation list?"
                - Checking configuration health before troubleshooting a campaign's MA destination
                - Before deciding whether to call set_default_ma_list or clear_default_ma_list

                RESPONSE FORMAT:
                Returns "status" as one of:
                - NOT_CONFIGURED: no default has ever been set
                - AVAILABLE: a default is set and resolves correctly (listId, provider, name populated)
                - PROVIDER_MISMATCH: the default was set for a provider the account is no longer
                  connected to (name is null; a different MA tool is connected now)
                - DISCONNECTED: the default was set but no MA tool is connected at all (name is null)
                - NOT_FOUND: the default list itself was deleted in the MA tool (name is null)
                Also returns "listId" and "provider".

                EXAMPLE: "What's the default MA list?" -> get_default_ma_list()

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context: the value is snapshotted once at campaign creation and is not a live reference. It also fully documents all possible status values with their meanings, which is far beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Although longer than average, the description is tightly organized into labeled sections: usage, when-to-use, response format, and example. Every sentence adds operational value, and the key purpose is stated immediately in the first line.

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?

With no output schema and no parameters, the description carries the full burden of explaining the response contract. It enumerates every status value, the presence or nullability of the returned fields (listId, provider, name), and gives a concrete example. Nothing needed for correct invocation is missing.

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 tool has zero parameters and the schema is empty, so the 0-param baseline of 4 applies. No parameter documentation is needed, and the example call reinforces that the tool takes no arguments.

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 a specific verb and resource: it gets 'the account's default marketing automation (MA) destination list.' It differentiates itself from siblings like list_marketing_automation_lists and search_ma_lists by focusing on the singular default destination, and from set_default_ma_list/clear_default_ma_list by being the read counterpart.

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 THIS TOOL' section explicitly lists user-intent triggers, configuration-health checks, and the decision point before calling set_default_ma_list or clear_default_ma_list. It also clarifies the non-live snapshot behavior so the agent won't incorrectly assume changes propagate retroactively.

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?