SFMC MCP Server

list_data_extensions

Retrieve Data Extensions from the connected Business Unit. Filter by name, paginate results, and optionally include field metadata such as name, type, size, primary key, and nullable status.

Instructions

Lista Data Extensions da Business Unit conectada, com nome, external key (customerKey), e opcionalmente os campos de cada uma. Suporta filtro por nome e paginação.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_data_extensions"
  }
}

Input Schema

Name	Required	Description
`page`	No	Página de resultados (começa em 1).
`pageSize`	No	Itens por página (máx 100).
`nameFilter`	No	Filtro parcial por nome da DE (case-insensitive). Ex: 'master' encontra 'Master_Contacts'.
`includeFields`	No	Se true, inclui a lista de campos (nome, tipo, tamanho, PK, nullable) de cada DE.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 14, 2026

TDQS

A4/5.0

Behavior3/5

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

The description discloses features like pagination, name filter, and optional fields, but does not mention permission requirements, rate limits, or confirm read-only behavior. Since no annotations are provided, the description carries the full burden, and it is adequate but not exhaustive.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, optional features, and filtering support. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately mentions the returned fields (name, external key, and optionally fields). The tool is simple and the description covers essential information for invocation. Could mention sorting or ordering, but not critical.

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%, so baseline is 3. The description adds that default returns include name and external key, but the parameter descriptions in the schema already cover the details. No significant value beyond 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 clearly states the tool lists Data Extensions from the connected Business Unit, with name and external key, and optionally fields. This distinguishes it from sibling tools query_data_extension and validate_sql, which serve different purposes.

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 implies use for listing Data Extensions with filtering and pagination, but does not explicitly state when not to use it versus alternatives. Since the siblings are distinct, the context is clear but lacks explicit exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server