SnoopScan

Create or change a mentions watch

watchMentions

Create a watch that looks for keywords on Reddit, Hacker News, Bluesky, YouTube, Threads, the web, GitHub, RSS or Atom feeds, news, Product Hunt, DEV, Slashdot and Lobsters, Stack Overflow, Lemmy and Misskey, podcasts, Substack, Discourse forums, review sites and Telegram channels on a schedule, and sorts each find into bug report, complaint, question, buying intent, praise or competitor. Give name and keywords to create one, or watchId plus the fields to change. competitors are extra keywords filed as competitor mentions; exclude removes posts containing those words; platforms limits the sources (reddit, hackernews, bluesky, youtube, threads, web, github, feeds, news, devfeeds, stackexchange, fediverse, podcasts, substack, forums, appreviews, telegram; default all); feeds are up to 10 feed addresses the feeds source reads for new entries that name a keyword; places are up to 10 web addresses the forums, appreviews and telegram sources read: a Discourse forum (new posts that name a keyword), a review page (appreviews: every new review is a mention, with its rating or thumbs under engagement): an App Store, Google Play, Trustpilot, Steam, Feefo, Reviews.io, Sitejabber, Yelp or Capterra link, or a public Telegram channel such as https://t.me/name (posts that name a keyword); intervalMinutes is 5 to 10,080 (default 15). Each answered source query is recorded on the account's usage. Read results with listMentions; try keywords first with testMentions.

Needs a free SnoopScan key.

Input Schema

Name	Required	Description	Default
`name`	No
`feeds`	No
`active`	No
`places`	No
`exclude`	No
`watchId`	No
`webhook`	No
`keywords`	No
`platforms`	No
`competitors`	No
`intervalMinutes`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / places

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Places"
+}

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / feeds

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Feeds"
+}

AddedOct 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the auth requirement ("Needs a free SnoopScan key") and a cost/quota side effect ("Each answered source query is recorded on the account's usage"), plus defaults for platforms and interval. The gap is update semantics: it never says whether passing `watchId` merges fields or replaces the whole watch, which matters for a non-idempotent write tool.

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?

The action and both modes are reasonably front-loaded, but the opening enumerates eighteen source platforms in one breath and the rest is a single run-on paragraph mixing creation, per-parameter semantics, and cross-references. The platform list is largely duplicated later by the `platforms` enum, so it does not all earn its place.

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

Completeness3/5

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

An output schema exists and auth/quota are covered, but for a create-or-update mutation with 11 optional parameters the description omits partial-update semantics and the purpose of `active` and `webhook`. Those are real gaps for correct invocation, not cosmetic ones.

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 description coverage is 0% and every parameter is nullable, so the description carries the full burden — and it does for 9 of 11 params, including enumerated platform names with a default, the 10-item caps on `feeds`/`places`, the meaning of `places` per source type, and the 5–10,080 interval range. `active` and `webhook` are never explained, leaving two parameters undocumented anywhere.

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?

Opens with a specific verb+resource ("Create a watch that looks for keywords ... on a schedule") and adds the classification behavior (bug report, complaint, question, buying intent, praise, competitor). It also distinguishes create vs. update mode via `name`+`keywords` versus `watchId`, which separates it from siblings like watchPages and listMentions.

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

Usage Guidelines5/5

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

Explicitly states both invocation modes ("Give `name` and `keywords` to create one, or `watchId` plus the fields to change") and routes to the correct alternatives: "Read results with `listMentions`; try keywords first with `testMentions`." That is a clear when-to-use-this vs. when-to-use-siblings statement.

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

All SnoopScan 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.