Response Trimming
Reduce token usage by 40-80% with two parameters available on all curated tools.
Parameters
fields — Select specific fields
Use dot-notation to pick only the fields you need:
{"fields": ["id", "properties.email", "properties.firstname"]}
This works on any response shape — the gateway intelligently applies field picking to array items inside results, records, or rows containers.
format — Strip metadata
| Value | Behavior |
|---|---|
full (default) | Returns the complete executor wrapper: {success, status, data: {...}} |
compact | Strips the wrapper, returns the data payload directly |
Examples
Full response (default)
{
"success": true,
"status": 200,
"data": {
"results": [
{"id": "1", "properties": {"email": "a@b.com", "firstname": "Alice", "phone": "555-1234", "createdate": "2025-01-01"}}
],
"paging": {"next": {"after": "2"}}
}
}
With format: "compact"
{
"results": [
{"id": "1", "properties": {"email": "a@b.com", "firstname": "Alice", "phone": "555-1234", "createdate": "2025-01-01"}}
],
"paging": {"next": {"after": "2"}}
}
With fields: ["id", "properties.email"]
{
"success": true,
"status": 200,
"data": {
"results": [{"id": "1", "properties": {"email": "a@b.com"}}],
"paging": {"next": {"after": "2"}}
}
}
Both combined
{
"results": [{"id": "1", "properties": {"email": "a@b.com"}}],
"paging": {"next": {"after": "2"}}
}
Provider-specific behavior
| Provider | Compact extracts |
|---|---|
| HubSpot | {results, paging} |
| Salesforce | {records, totalSize, done} |
| GA4 | rows array |
| Google Ads | First result set's results array |
| Others | data payload from executor wrapper |