search_insights_criteria_fields
Discover available fields for building insights filter criteria.
Read analytics
Returns data. Calling it changes nothing, so it is safe in an unattended loop.
What it does
Discover available fields for building insights filter criteria. USE BEFORE: get_insights_report or create_segment when filtering is needed. WORKFLOW: 1. Extract keywords from user request (3-10 recommended) 2. Call this tool with keywords 3. Use returned field definitions to build criteria KEYWORD EXAMPLES: - URL/visits → ["page", "url", "visit", "web"] - Engagement → ["score", "engagement", "activity"] - CRM → ["crm", "salesforce", "opportunity"] - Channels → ["linkedin", "facebook", "google"] RESPONSE: Returns fields with name, label, type, operators, and options. FIELD TYPES: MULTIPICKLIST, PICKLIST, STRING, NUMERIC, DATE, BOOLEAN, RANGE, ARRAY, DYNAMIC
Arguments
| Argument | Type | Notes | |
|---|---|---|---|
search_keywords |
array | required | Keywords to search for fields (3-10 recommended). E.g., ['page', 'url', 'visit'] |
Request
curl
curl -s -X POST https://mcp-server.metadata.io/mcp \
-H "Authorization: $METADATA_PAT" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2025-11-25" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_insights_criteria_fields","arguments":{"search_keywords":[]}}}'Response
Recorded with these arguments. Enum values are the first the tool's own schema
declares; ids were fetched live from a list_ call immediately before.
arguments used
{
"search_keywords": [
"page",
"url",
"visit"
]
}Real, from the production server, in 808 ms. Values that identify a customer or disclose money are replaced with typed placeholders; keys, types and nesting are exactly as returned.
recorded response
"[value redacted]"Related
Other analytics tools: