Metadata MCP Connector

Get ABM Account Lists

get_abm_account_lists

Read-only

Get account lists from the Metadata ABM Lists library. Retrieves uploaded CSV account lists, website retargeting lists, and their metadata.

            WHEN TO USE:
            - List all available account lists with pagination and filtering
            - Search for specific account lists by filename
            - Review account list details including status, type, and account counts
            - Find lists by type (CSV, WEBSITE_RETARGETING, etc.)
            - Check list readiness and report status

            PARAMETERS:
            - filename: Filter by filename (partial matching)
            - page: Page number (default: 0)
            - size: Results per page (default: 100, max: 100)
            - sort: Sort criteria (default: "createdDate,desc")
            - status: Filter by status (READY, PROCESSING, etc.)
            - type: Filter by type (CSV, WEBSITE_RETARGETING, etc.)

            RESPONSE INCLUDES:
            - List metadata (id, name, filename, status, type)
            - Account counts and audience associations
            - Creation dates and file hashes
            - Native targeting status
            - Account report status

            EXAMPLES:
            - get_abm_account_lists() - Get all account lists
            - get_abm_account_lists(filename="test_acl.csv") - Find specific list
            - get_abm_account_lists(type="CSV") - Get only CSV lists
            - get_abm_account_lists(status="READY") - Get ready lists

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number for pagination (0-based)
`size`	No	Number of results per page
`sort`	No	Sort criteria (e.g., 'createdDate,desc', 'name,asc', 'accountsCount,desc')	createdDate,desc
`type`	No	Filter by list type (e.g., CSV, WEBSITE_RETARGETING)
`status`	No	Filter by status (e.g., READY, PROCESSING, ERROR)
`filename`	No	Filter by account list filename (supports partial matching)

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 16, 2026

TDQS

A4.4/5.0

Behavior4/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 useful behavioral context by describing retrieval semantics, supported filters, and response contents such as account counts, audience associations, creation dates, and file hashes. This is valuable given there is no output schema to describe the return envelope.

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 well-structured with clear sections for when to use, parameters, response contents, and examples, and it front-loads the core purpose. It is somewhat long and repeats some parameter information already in the schema, but each section contributes useful decision support.

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 read-only list tool with six optional parameters and no output schema, the description covers enough context: use cases, parameter behavior, response contents, and examples for common calls. The annotations cover safety, and the description fills the output format gap since no output schema exists.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by giving example values for type and status (e.g., CSV, WEBSITE_RETARGETING, READY, PROCESSING), default values, and concrete usage examples for each parameter beyond the schema's 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 description names the specific verb 'Get account lists from the Metadata ABM Lists library' and clarifies the exact resource scope, including CSV lists, website retargeting lists, and their metadata. It also lists distinct operations such as listing, filtering by filename, and type, which distinguishes it from many sibling tools.

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 WHEN TO USE section clearly enumerates use cases: listing all account lists, searching by filename, reviewing details, filtering by type, and checking readiness. It provides strong context but does not explicitly name sibling tools or state when not to use this tool.

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?