Metadata MCP Connector

Clear Default Marketing Automation List

clear_default_ma_list

Destructive

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

                USAGE INSTRUCTIONS FOR LLM:
                WARNING: this only affects future campaign creation. Channels that already
                inherited the default at creation time keep their snapshotted value unchanged —
                clearing the default never retroactively removes it from existing channels.

                WHEN TO USE THIS TOOL:
                - User wants to stop new campaign channels from inheriting a default MA list
                - User wants to unset the default before setting a different one

                RESPONSE FORMAT:
                Returns {"status": "CLEARED", "listId": null, "provider": null, "name": null}.

                EXAMPLE: "Clear the default marketing automation list" -> clear_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.6/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses a critical behavioral nuance: existing channels keep their snapshotted value and are unaffected. It also gives the exact response format ({"status": "CLEARED", ...}), which adds meaningful transparency beyond the structured 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 structured and front-loaded with the core purpose, and the warning about future-only effects is essential. However, the WHEN-TO-USE and EXAMPLE sections partially restate the opening sentences, making it slightly more verbose than necessary for a zero-parameter tool.

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 zero-parameter destructive tool, the description is complete: it states what the tool does, when to use it, the important non-retroactive behavior, and the exact response format. Since there is no output schema, disclosing the response shape is appropriate and valuable.

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 already reflects this with 100% coverage. The description confirms the no-argument call via its example, which adds slight clarity but does not need to do more since there are no parameters to explain.

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 opens with a specific verb + resource: "Clear the account's default marketing automation (MA) destination list." This clearly distinguishes the tool from siblings like get_default_ma_list and set_default_ma_list, and the example reinforces the intended action.

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?

Explicit 'WHEN TO USE THIS TOOL' conditions are provided: stopping future campaign channels from inheriting the default, and unsetting the default before setting a different one. It also warns that clearing only affects future campaign creation and never retroactively removes the list from existing channels. It does not explicitly name alternative tools, but the usage context is clear.

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?