generate_export_spec
MCP server · Local · nothing leaves your machine
Which columns may leave your org and which never may, how to derive the email domain, and how to build the conversion label. Set warehouse to snowflake or databricks and you get a commented SQL scrub template instead of spreadsheet steps.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
crm | string | Yes | |
objects | array | Yes | |
date_range | any | No | |
warehouse | string | No | |
tables | any | No |
What it returns
The columns that may leave the org and the ones that never may, with the scrub steps for each object - or a commented SQL template when a warehouse is named - and how to build the conversion label.
Credential
None. This tool runs entirely inside the agent: it makes no network call, needs no credential, and sends none of what you pass it anywhere.
Network call: no. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call generate_export_spec: which columns may leave your org and which never may, how to derive the email domain, and how to build the conversion label.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "generate_export_spec", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.
Notes
- The scrub is not decoration: record ids are hashed so returned scores still join back to the CRM, email addresses are reduced to the domain with the local part stripped, and dates are truncated to the calendar day.