Write a query from a description
query_suggest_postWrite or refine a Boolean social media query from a plain-language monitoring brief, test it against example posts, and preview validation before searching.
Instructions
Write a Boolean query from a plain-language description of what to monitor, optionally with example posts it should and shouldn't find, or refine an existing query. The query is written by AI, then read, explained and planned like validate, and run over the example posts. Show it to the user before searching with it. 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": {
"brief": "<brief>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "query_suggest_post"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| brief | Yes | What to monitor, in plain words and any language: brands, people, topics, places, what to leave out. With `previousQuery`, the change to make to that query, such as `also exclude job ads`. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| examples | No | Example posts, to check the query against and to help write it. | |
| explainIn | No | Language of the explanation, the note and the refusal: `en` (default) or `es`. | |
| languages | No | Languages the posts should be in, as two-letter ISO 639-1 codes. Any language when omitted. | |
| 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, for the plan and its estimate. Default 100. | |
| previousQuery | No | A query in Social Fetch's syntax to refine as `brief` asks, instead of writing a new one. | |
| 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. |