SFMC MCP Server

query_data_extension

Retrieve records from a Data Extension by external key. Apply filters, sort, and paginate results, with up to 50 rows per call.

Instructions

Consulta registros de uma Data Extension pelo external key (customerKey). Suporta filtro simples (ex: "Status eq 'Active'"), ordenação e paginação. Retorna no máximo 50 linhas por chamada para não estourar o contexto.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "externalKey": "<externalKey>"
    },
    "name": "query_data_extension"
  }
}

Input Schema

Name	Required	Description
`page`	No	Página de resultados.
`filter`	No	Filtro no formato do SFMC: campo operador valor. Operadores: eq, ne, gt, lt, ge, le, like. Ex: "EmailAddress like '%gmail%'" ou "SubscriberKey eq '12345'".
`orderBy`	No	Campo e direção de ordenação. Ex: 'CreatedDate desc'.
`pageSize`	No	Linhas por página (máx 50).
`externalKey`	Yes	External key (customerKey) da Data Extension.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 14, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description partially compensates by mentioning pagination (max 50 rows), filter operators, and ordering. However, it lacks details on side effects (e.g., read-only guarantee), error conditions, or authorization requirements.

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 two sentences, front-loaded with the main purpose, and covers all essential features without waste. Each sentence contributes meaning.

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

Completeness3/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 could better explain the response structure or field selection. It is adequate for a simple query tool but lacks details on error handling or data format.

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 baseline is 3. The description adds value by explaining the filter format with examples, pagination limits, and ordering syntax, going beyond the schema's parameter 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 clearly states it queries records from a Data Extension by external key, supporting filter, ordering, and pagination. It distinguishes from sibling tools list_data_extensions and validate_sql by specifying this tool is for querying specific records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives. It does not mention that list_data_extensions should be used for listing Data Extensions or validate_sql for SQL validation. Usage context is only implied.

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

Deploy Server