@nooticr/mcp 1.26.30 → 1.26.31

package/dist/shared/evidence.js

@@ -563,3 +563,56 @@ export function fetchBillingNote(tool) {
         "not charge again: the idempotency key is namespaced per tool, so a retry replays the " +
         "same debits.");
 }
+/**
+ * The searchable core of a complaint, with the speaker stripped out.
+ *
+ * `find_people_with_problem` widens a problem into the shapes a complaint
+ * takes. Those shapes were templated onto the raw argument, and the argument
+ * the schema asks for is a full sentence with a subject ("I waste an hour a
+ * day checking what competitors posted") — so "is there a way to " + that
+ * produced a string nobody has ever written, and sent it to a keyword search
+ * (#60).
+ *
+ * Two things happen here, and neither is intent matching — the backend is a
+ * keyword search and this does not pretend otherwise:
+ *
+ *  - The first-person subject and its auxiliary come off the front of each
+ *    clause. "I'm out of content ideas" is a sentence about a speaker;
+ *    "out of content ideas" is what the post being looked for actually says.
+ *  - The result is capped, because a long sentence matches on its commonest
+ *    words. That is the tool's own advice to its caller, and it was not
+ *    taking it.
+ *
+ * A caller who can do better should: `queries` overrides all of this.
+ */
+export function complaintCore(problem) {
+    const MAX_WORDS = 12;
+    // The pronoun always goes. The verb after it goes ONLY if it is an
+    // auxiliary — "I have no idea" is about a speaker, but "I waste an hour a
+    // day" carries "waste", and stripping it leaves "an hour a day checking",
+    // which is a worse search than the one being fixed. That distinction is the
+    // whole of this function; getting it wrong trades one bad query for another.
+    const SUBJECT = /^\s*(?:i|we)\b['’]?(?:m\b)?[\s,]*/i;
+    const AUXILIARY = /^\s*(?:am|are|is|was|were|have|has|had|do|does|did|don['’]?t|can['’]?t|cannot|been)\b[\s,]*/i;
+    // Never end on a word that was pointing at the one the cap removed.
+    const DANGLING = /(?:\s+(?:for|my|our|the|a|an|of|to|and|or|with|in|on|at|by|that|this))+$/i;
+    const cleaned = problem
+        .split(/[,;]+/)
+        .map((clause) => {
+        const withoutSubject = clause.trim().replace(SUBJECT, "");
+        // Only strip an auxiliary that actually followed a subject, so a clause
+        // opening with a real verb keeps it.
+        return (withoutSubject === clause.trim()
+            ? withoutSubject
+            : withoutSubject.replace(AUXILIARY, "")).trim();
+    })
+        .filter(Boolean)
+        .join(", ");
+    const words = (cleaned || problem.trim()).split(/\s+/).filter(Boolean);
+    return words
+        .slice(0, MAX_WORDS)
+        .join(" ")
+        .replace(/[,;]+$/, "")
+        .replace(DANGLING, "")
+        .trim();
+}

package/dist/shared/jobs.js

@@ -56,7 +56,7 @@
 import { z } from "zod";
 import { OUTPUT_SCHEMAS } from "./output-schemas.js";
 import { platformFromUrl, postSlug } from "./comment-review.js";
-import { clamp, handleMissGuidance, ownIt, PLATFORM_ARG } from "./evidence.js";
+import { clamp, complaintCore, handleMissGuidance, ownIt, PLATFORM_ARG } from "./evidence.js";
 import { withEvidence } from "./evidence-digest.js";
 import { confirmSpend, costOf, declinedResult, MAX_SPOKEN_HANDLE_CALLS, MAX_SPOKEN_TRANSCRIPTS, SPOKEN_PLATFORMS, CREDITS_PER_CREATOR, } from "./spend.js";
 import { distributionOf, excluding, numberOf, standing, } from "./performance.js";
@@ -2112,6 +2112,14 @@ export function registerJobTools(server, makeClient, store) {
                 .optional()
                 .describe("Where to look (default reddit). Each one is a separate paid search."),
             limit: z.number().int().optional().describe("Posts per query shape (default 6, max 15)."),
+            queries: z
+                .array(z.string())
+                .optional()
+                .describe("Search these exact phrasings instead of the ones derived from `problem` (max 4). " +
+                "You are better at this than a string template is: write how a person would " +
+                "actually word the complaint on the network being searched — a Reddit title, " +
+                "an X post — and keep each one short, because this is a keyword search and a " +
+                "long sentence matches on its commonest words."),
         })
             .strict(),
     }, async (args, extra) => {
@@ -2123,11 +2131,27 @@ export function registerJobTools(server, makeClient, store) {
         // The shapes a complaint takes, rather than the topic it is about. Kept
         // to three: each is a paid call per platform, and past three they start
         // returning the same posts as each other.
-        const shapes = [
-            { shape: "plain", query: problem },
-            { shape: "shared", query: `anyone else ${problem}` },
-            { shape: "asking", query: `is there a way to ${problem}` },
-        ];
+        //
+        // Built from a stripped core rather than the raw sentence, and the two
+        // non-plain shapes no longer prefix a template onto whatever arrived.
+        // The old `is there a way to ${problem}` assumed a bare verb phrase
+        // while the schema's own example is a full sentence with a subject, so
+        // the documented input produced "is there a way to I have no idea what
+        // to post next, I'm out of content ideas for my page" — a string nobody
+        // has ever written, sent to a keyword search, three times, having been
+        // lengthened twice (#60).
+        const core = complaintCore(problem);
+        const shapes = args.queries?.length
+            ? args.queries.slice(0, 4).map((q, i) => ({ shape: `given:${i + 1}`, query: q.trim() }))
+            : [
+                { shape: "plain", query: core },
+                // Reddit's own idiom, and it reads as a sentence now that `core`
+                // has had its leading subject removed.
+                { shape: "shared", query: `anyone else ${core}` },
+                // A SUFFIX, not a prefix: appended keywords cannot be made
+                // ungrammatical by whatever shape the core turned out to be.
+                { shape: "asking", query: `${core} any recommendations` },
+            ];
         const seen = new Set();
         const posts = [];
         const unavailable = [];
@@ -2199,9 +2223,20 @@ export function registerJobTools(server, makeClient, store) {
                 "and say how many you rejected and why — a shortlist with no reject count reads as if " +
                 "the search was precise.",
             "",
-            "`foundBy` says which phrasing surfaced each post: `plain` the problem itself, `shared` " +
-                "the does-anyone-else form, `asking` the is-there-a-tool form. The last two skew " +
-                "towards genuine complaints and the first towards content about the topic.",
+            args.queries?.length
+                ? "`foundBy` says which of your own phrasings surfaced each post, in the order you " +
+                    "gave them."
+                : "`foundBy` says which phrasing surfaced each post: `plain` the problem itself, " +
+                    "`shared` the does-anyone-else form, `asking` the looking-for-a-tool form. The " +
+                    "last two skew towards genuine complaints and the first towards content about " +
+                    "the topic.",
+            "",
+            args.queries?.length
+                ? ""
+                : `These were searched as: ${shapes.map((sh) => `"${sh.query}"`).join(", ")}. That ` +
+                    "is a keyword search, not intent matching. If those read wrong for where you are " +
+                    "looking — a Reddit title is worded differently from an X post — call this again " +
+                    "with `queries` set to phrasings you write yourself, and keep each one short.",
             "",
             unavailable.length
                 ? `Note that ${unavailable.length} searches errored — tell the user which networks ` +

package/dist/shared/tools-def.js

@@ -394,7 +394,7 @@ export const TOOL_DEFINITIONS = [
         name: "find_people_with_problem",
         title: "Find People With A Problem",
         description: "Find people describing a problem in their own words — prospects, early users, anyone whose complaint your product answers. Say the problem the way a person would say it (\"I spend hours checking competitors by hand\") and this searches for posts shaped like that complaint, not for the topic it is about. That difference is the point: searching the TOPIC finds marketing about it, which is what discover_social_posts is for. Widens the query into the forms a complaint takes — the plain phrasing, the does-anyone-else question, the is-there-a-tool ask — and merges what each returns. It is a wide cheap net and NOT a filter: the posts come back for you to judge, and many will be off-target. Consumes 2 nooticr credits per platform searched. Defaults to reddit, where people describe workflow pain in sentences; add twitter for volume.",
-        inputSchema: z.object({ problem: z.string().describe("The problem in a person's own words, not a topic. \"I waste an hour a day checking what competitors posted\" finds people; \"competitor analysis\" finds marketing about competitor analysis."), platforms: z.array(z.enum(["reddit", "twitter", "youtube", "tiktok", "instagram", "linkedin"])).optional().describe("Where to look (default reddit). Each one is a separate paid search."), limit: z.number().int().optional().describe("Posts per query shape (default 6, max 15).") }).strict(),
+        inputSchema: z.object({ problem: z.string().describe("The problem in a person's own words, not a topic. \"I waste an hour a day checking what competitors posted\" finds people; \"competitor analysis\" finds marketing about competitor analysis."), platforms: z.array(z.enum(["reddit", "twitter", "youtube", "tiktok", "instagram", "linkedin"])).optional().describe("Where to look (default reddit). Each one is a separate paid search."), limit: z.number().int().optional().describe("Posts per query shape (default 6, max 15)."), queries: z.array(z.string()).optional().describe("Search these exact phrasings instead of the ones derived from `problem` (max 4). You are better at this than a string template is: write how a person would actually word the complaint on the network being searched \u2014 a Reddit title, an X post \u2014 and keep each one short, because this is a keyword search and a long sentence matches on its commonest words.") }).strict(),
     },
     {
         name: "search_spoken_mentions",

package/dist/shared/tools.js

@@ -26,7 +26,7 @@ import { loadingPlansJson } from "./loading-plans.js";
 import { registerHandoff } from "./handoff.js";
 import { registerCollabTools } from "./collab.js";
 /** Current MCP server version — bumped on every deploy for traceability. */
-export const MCP_SERVER_VERSION = "1.26.30";
+export const MCP_SERVER_VERSION = "1.26.31";
 /** MCP Apps extension identifier */
 const UI_EXTENSION = "io.modelcontextprotocol/ui";
 /** MIME type for MCP Apps HTML resources */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@nooticr/mcp",
   "mcpName": "com.nooticr/mcp",
-  "version": "1.26.30",
+  "version": "1.26.31",
   "description": "MCP server for nooticr - fetch, discover and understand TikTok/Instagram/YouTube/X/Reddit/LinkedIn/Weibo posts with AI (media metadata, niche discovery, brand monitoring, hook & viral analysis)",
   "homepage": "https://mcp.nooticr.com",
   "repository": {