Save Query
save-mcp-queryUse when the user wants to save discovery or enrichment results for later — e.g., "save these results" or "I want to come back to this list."
Saves MCP results as a thin wrapper query visible in the app UI. Data should contain at minimum a domain column, plus any custom columns to preserve (similarity scores, MCP-computed fields, etc.).
Valid action values: ['discover', 'segment', 'contacts', 'append', 'match']
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": {
"input": "<input>"
},
"name": "save-mcp-query"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| input | Yes | Request model for saving result rows as a thin-wrapper saved query. Shared by the REST `POST /queries/save-results` endpoint and the `save-mcp-query` MCP tool so the payload shape stays identical. | |
| context | No | Why you are calling this tool, in a few words. No names or emails. | |
| llm_model | No | Your model id, or "unknown". | |
| conversation_id | No | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _mcp_instructions | No | Server-issued metadata for this conversation. |