Metadata MCP Connector

Search Marketing Automation Lists

search_ma_lists

Read-only

Search the connected marketing automation (MA) tool's destination lists by name.

                USAGE INSTRUCTIONS FOR LLM:
                Use this to find a concrete marketing-automation list before setting it as the
                account's default destination list. This tool is the ONLY safe way to resolve a
                list id: never invent, guess, or reuse a list id from memory or from a different
                account. Always call this first, confirm the match with the user if there are
                several, and pass the exact "listId" from the result to set_default_ma_list.

                WHEN TO USE THIS TOOL:
                - User wants to set or change the default marketing automation destination list
                - User asks "which MA lists do we have?" or "find the list named X"
                - Before calling set_default_ma_list

                RESPONSE FORMAT:
                Returns {"lists": [{"listId": int, "name": str}, ...]}. An empty array means no
                marketing automation tool is connected, or nothing matched the search text.

                EXAMPLE: "Set the default MA list to Newsletter Signups" -> search_ma_lists(name="Newsletter Signups")
                then set_default_ma_list(list_id=<matched listId>)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Free-text search string to filter destination lists by name.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral safeguards: it is the only safe way to resolve a list id, warns against inventing/guessing IDs, instructs confirming matches with the user, and discloses the exact response format including empty-array semantics. 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.

Conciseness5/5

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

The description is longer than average but well-structured with labeled sections: summary, usage instructions, when-to-use bullets, response format, and a concrete example. Every section earns its place, and the safety-critical guidance is front-loaded.

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?

This is a simple one-parameter read-only tool, and the description fully compensates for the missing output schema by specifying the exact response shape and empty-array meaning. It also covers the pre-call workflow, matching behavior with multiple results, and the follow-up set_default_ma_list call, leaving nothing essential missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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

Schema coverage is 100%, and the schema already documents 'name' as a free-text search string, so the baseline is 3. The description adds an example invocation and clarifies the output shape, but it does not meaningfully extend the parameter's semantics beyond the schema.

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 states a specific verb ('Search'), a clear resource ('connected marketing automation (MA) tool's destination lists'), and a filtering criterion ('by name'). This is distinct from sibling tools like list_marketing_automation_lists, and the example makes the intended operation unambiguous.

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?

The description provides explicit WHEN TO USE bullets, including 'User wants to set or change the default marketing automation destination list' and 'Before calling set_default_ma_list'. It does not explicitly contrast itself against list_marketing_automation_lists, and one recommended use case ('which MA lists do we have?') is slightly mismatched with a required 'name' parameter.

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?