Validate a Boolean query
query_validate_postCheck a Boolean query before searching: read or import it from other tools, get a plain-language explanation, see how each platform would search it, what won't be covered, and the estimated credits.
Instructions
Check a Boolean query before searching: read it (or import it from Talkwalker, Brandwatch, Meltwater, Onclusive or X, or detect which), explain it in English or Spanish, and see how it would be searched on each platform, what won't be covered and the estimated credits. Free.
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": {
"query": "<query>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "query_validate_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The Boolean query to check. | |
| since | No | Earliest post time, between 2000 and 2100. Overrides a date in an imported query. | |
| until | No | Latest post time, between 2000 and 2100, not before `since`. Overrides a date in an imported query. | |
| syntax | No | Syntax the query is written in: `native` (Social Fetch's Boolean language), another tool's to import (`x`, `onclusive`, `talkwalker`, `brandwatch` or `meltwater`), or `auto` to detect it from the query. With `auto`, `detected` says which was used and why. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| language | No | Language of the explanation: `en` (default) or `es`. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| platforms | No | Platforms to plan for. Every platform when omitted. | |
| maxCredits | No | Credits a search would be allowed, shared evenly between the platforms with something to search; the plan and the estimate are shaped by it. Default 100. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. | |
| platformSearches | No | Searches to plan on a platform instead of those planned from the query, by platform, as `POST /v1/query/search` would run them. |