Ignix

Create a listening search

create_saved_search

Watch for mentions of the brand (or a competitor, or a topic) on X or in the NEWS (press and blogs via Google News; the brand's own website is left out). Reddit is paused while Reddit's API is closed to third-party apps. X is checked every 6 hours and news once a day; neither needs a connected account. On X the query is passed through untouched, so X operators work ("exact phrase", OR, -is:retweet, lang:es) and only posts that contain the words are kept. Instagram, TikTok and YouTube are not watched. With kind "opportunity" (X) it looks for people asking for what the business sells and Sparky drafts a reply for the user to approve; nothing is posted on its own. Inferno plan only.

Input Schema

Name	Required	Description
`kind`	No	"mention" (default): mentions of the brand, a competitor or a topic. "opportunity" (X only): search a TOPIC the way someone looking for help would write it; for each post the AI decides whether the author is asking for something this business offers and, if so, Sparky drafts a helpful public reply that discloses the brand. Nothing is ever posted on its own: the user approves each reply (reply_to_mention with the draft).
`name`	No	Optional label for the search.
`query`	Yes	What to watch for. On X, X search operators work ("exact phrase", OR, -is:retweet, lang:es).
`platform`	Yes	Where to watch: twitter (X) or news.
`workspaceId`	No	Workspace to work on (an id from list_workspaces). Not needed when this connection is tied to one workspace, or when you pass an account: the account's workspace is used.
`idempotencyKey`	No	Optional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / platform / enum

Previous value: -[
-  "twitter",
-  "reddit",
-  "news"
-]New value: +[
+  "twitter",
+  "news"
+]

removedInput schema / properties / subreddit

Removed value: -{
-  "description": "Reddit only: narrow to one subreddit.",
-  "type": "string"
-}

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / kind / description

Previous value: -"\"mention\" (default): mentions of the brand, a competitor or a topic. \"opportunity\" (X and Reddit only): search a TOPIC the way someone looking for help would write it; for each post the AI decides whether the author is asking for something this business offers and, if so, Sparky drafts a helpful public reply that discloses the brand. Nothing is ever posted on its own: the user approves each reply (reply_to_mention with the draft)."New value: +"\"mention\" (default): mentions of the brand, a competitor or a topic. \"opportunity\" (X only): search a TOPIC the way someone looking for help would write it; for each post the AI decides whether the author is asking for something this business offers and, if so, Sparky drafts a helpful public reply that discloses the brand. Nothing is ever posted on its own: the user approves each reply (reply_to_mention with the draft)."

changedInput schema / properties / platform / description

Previous value: -"Where to watch: twitter (X), reddit or news."New value: +"Where to watch: twitter (X) or news."

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / kind

Added value: +{
+  "description": "\"mention\" (default): mentions of the brand, a competitor or a topic. \"opportunity\" (X and Reddit only): search a TOPIC the way someone looking for help would write it; for each post the AI decides whether the author is asking for something this business offers and, if so, Sparky drafts a helpful public reply that discloses the brand. Nothing is ever posted on its own: the user approves each reply (reply_to_mention with the draft).",
+  "enum": [
+    "mention",
+    "opportunity"
+  ],
+  "type": "string"
+}

AddedOct 18, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true) it discloses substantial runtime behavior: X polled every 6 hours, news once a day, no account connection required, news sourced via Google News with the brand's own site excluded, and that 'opportunity' mode only drafts replies for user approval and never posts on its own. That is exactly the mutation-safety context an agent needs and cannot get from the structured fields.

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

Conciseness4/5

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

Purpose and platform scope are front-loaded, and the dense single paragraph carries mostly load-bearing detail (cadence, plan gating, approval-only drafting). A few nested parentheticals and the Reddit-API aside add length without helping the call decision, but nothing is badly out of order.

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 a creation tool with no output schema and full schema description coverage, the description covers what is created, where it runs, how often, and the plan prerequisite. It stops short of saying whether the search is active immediately on creation and whether duplicate searches or a count limit are handled.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents platform, query operators, kind and idempotencyKey, setting the baseline at 3. The description adds real meaning on top — X queries are passed through untouched and only word-containing posts are kept, and the brand's own site is excluded from news — though it restates the operator list from the schema.

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

Purpose4/5

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

The description states the effect concretely — watching for brand/competitor/topic mentions on X and NEWS — with explicit scope limits (no own website, Instagram/TikTok/YouTube not watched) that distinguish it from list_saved_searches or list_mentions. The creation verb itself is implied by the name/title rather than stated in the body, which keeps it just short of a 5.

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?

It gives clear conditions for use (watch brand, competitor or topic on the two supported platforms) and explicit exclusions — Instagram, TikTok, YouTube unwatched, Reddit paused — plus the 'Inferno plan only' prerequisite and that no connected account is needed. It never names a sibling tool as an alternative or says when to prefer an existing search over a new one.

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

All Ignix tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?