Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Validate a Boolean query

query_validate_post
Read-onlyIdempotent

Check 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

NameRequiredDescriptionDefault
queryYesThe Boolean query to check.
sinceNoEarliest post time, between 2000 and 2100. Overrides a date in an imported query.
untilNoLatest post time, between 2000 and 2100, not before `since`. Overrides a date in an imported query.
syntaxNoSyntax 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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
languageNoLanguage of the explanation: `en` (default) or `es`.
llm_modelYesThe 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.
platformsNoPlatforms to plan for. Every platform when omitted.
maxCreditsNoCredits 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_idNoEcho 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.
platformSearchesNoSearches to plan on a platform instead of those planned from the query, by platform, as `POST /v1/query/search` would run them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds genuinely new behavior: the call is "Free" (no credit charge), it reports "what won't be covered", and it returns per-platform search plans plus an estimated credit cost. It does not mention the conversation_id handshake or output shape, but the parameter schema documents the former.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence front-loaded with the core purpose, and each clause earns its place by naming a distinct capability. However, the colon-and-parenthetical list of five import platforms plus an embedded "or detect which" makes it dense and harder to scan than a short sentence plus a bulleted capability list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with nested objects and no output schema, the description does the work of explaining what comes back: a reading, an explanation, per-platform search plans, uncovered areas and a credit estimate. The notable omission is the two-phase conversation_id flow, which only appears as a parameter description and is unhelpful to discover late.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the schema already documents all 11 parameters thoroughly, including the syntax enum, platform list, maxCredits and platformSearches. The description corroborates a few of these (importing from Talkwalker/Brandwatch/Meltwater/Onclusive/X maps to the syntax enum; "estimated credits" maps to maxCredits; per-platform searching maps to platforms/platformSearches) but adds no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource, "Check a Boolean query before searching", and then enumerates the concrete outputs: reading/importing the query, an English or Spanish explanation, per-platform search plans, coverage gaps and a credit estimate. This is clearly a pre-flight validation tool, distinguishable from the sibling query_search_post which actually retrieves posts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Check a Boolean query before searching" gives clear timing guidance (run this first, then search), and the enumerated outputs make the situations it serves obvious. It stops short of naming the alternative tool to call afterwards or stating when it can be skipped, so a 5 is not warranted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools