@nooticr/mcp 1.26.54 → 1.26.56

package/README.md

@@ -52,7 +52,7 @@ npx @nooticr/mcp login   # one-time sign-in (Google)
 
 ## Tools
 
-88 tools, grouped by what you are trying to do. Prices are in nooticr credits and
+90 tools, grouped by what you are trying to do. Prices are in nooticr credits and
 match what the server actually charges.
 
 The job tools under **Answer a question you actually have** are not
@@ -78,11 +78,11 @@ them caps that fan-out with an argument.
 | `analyze_post_fast` | 2 | The post's transcript, caption and stats — everything but the pictures, which is what makes it the cheap read. Two fetches: `get_social_media` (1) and `get_post_transcript` (1). The sensible default. |
 | `analyze_post` | 3 | Frames sampled across the video, as **images your model can actually look at**, plus the transcript. Two fetches: `get_post_frames` (2) and `get_post_transcript` (1). Use when the visuals are the point — framing, editing, on-screen text. |
 | `understand_social_post` | 3 | The same two fetches, asked for a description of what physically happens on screen rather than why it works. Use when you need the events, not the strategy. |
-| `analyze_comments` | 2 | The comment section, every comment with a stable id, and the taxonomy to label them with — sentiment, and whether each is praise, a complaint, a bug report, a question, a request, a comparison or spam. The same `get_post_comments` call, at the same price as reading them directly. Pass `verbatim: true` to have every item rendered whole for quoting rather than clipped to fit; same price. |
+| `summarize_post_comments` | 2 | The comment section, every comment with a stable id, and the taxonomy to label them with — sentiment, and whether each is praise, a complaint, a bug report, a question, a request, a comparison or spam. The same `get_post_comments` call, at the same price as reading them directly. Pass `verbatim: true` to have every item rendered whole for quoting rather than clipped to fit; same price. |
 | `show_comment_review` | free | Draws the classifications your model produced — every comment with its sentiment and category, filterable and selectable. Makes no requests; it only renders what you pass it. |
 | `show_post_analysis` | free | Draws the analysis your model wrote from `analyze_post`/`analyze_post_fast`/`understand_social_post` — hook strength, script structure, quotable lines, suggested hashtags and more, whichever fields you produced. Makes no requests; it only renders what you pass it. |
-| `compare_posts` | 1 | The first of two to five posts, fetched with its stats, and the comparison left to you. Fetch the rest with `get_social_media` at 1 credit each. Use when performance differs and you need to know why. |
-| `show_compared_posts` | free | Draws the comparison your model wrote from `compare_posts` — each post scored, the winner marked, what differed and the next test worth running. Makes no requests; it only renders what you pass it. |
+| `compare_social_posts` | 1 | The first of two to five posts, fetched with its stats, and the comparison left to you. Fetch the rest with `get_social_media` at 1 credit each. Use when performance differs and you need to know why. |
+| `show_compared_posts` | free | Draws the comparison your model wrote from `compare_social_posts` — each post scored, the winner marked, what differed and the next test worth running. Makes no requests; it only renders what you pass it. |
 
 ### Research a niche or a creator
 
@@ -124,7 +124,7 @@ them caps that fan-out with an argument.
 | `who_should_i_work_with` | 2, or 4 with a seed | A collaboration shortlist: a keyword search merged with the lookalikes of a creator who already fits, marked by which search found each one. Every candidate also carries the **links pulled out of their bio**, typed and sorted by how much opening one will tell you — a repository to read the code in, their own site, a link hub that holds the real links — so vetting is reading the work rather than re-reading the follower count. Those links are never fetched here: they came out of a field the person being evaluated controls, so the host opens them, and the result says so. It does **not** measure audience overlap — that costs about nine credits a candidate, so the result says so and shows how to check a finalist rather than faking the signal. |
 | `find_people_with_problem` | 6 per platform | 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 and it searches for posts shaped like that complaint rather than for the topic it is about: 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 marks which one surfaced each post. A wide cheap net and **not** a filter: the posts come back for you to judge, and plenty will be off-target. Defaults to reddit, where people describe workflow pain in sentences. Each platform is searched once per query shape — three by default, at 2 credits a search. Not searchable here: linkedin, which has no keyword post search upstream. Pass `verbatim: true` to have every item rendered whole for quoting rather than clipped to fit; same price. |
 | `show_collab_shortlist` | free | Draws the candidates you scored, ranked, and asks the user which to approach. The scores are attributed to your model, not presented as a nooticr rating, and a candidate scored without anything having been opened is marked unverified. Makes no requests. |
-| `why_did_this_underperform` | 3 | One post against the creator's own recent distribution, with the post taken back out of its own baseline. Returns median, quartiles, ratio and percentile, so the answer can be "this is an ordinary result, not a failure". Different question from `compare_posts`, which weighs two URLs you already picked. |
+| `why_did_this_underperform` | 3 | One post against the creator's own recent distribution, with the post taken back out of its own baseline. Returns median, quartiles, ratio and percentile, so the answer can be "this is an ordinary result, not a failure". Different question from `compare_social_posts`, which weighs two URLs you already picked. |
 | `what_should_i_make_next` | 2 + 2 per post read + 2 (12 by default) | Demand against supply: what your commenters explicitly ask for, set beside what a niche sweep shows is already being made. A gap nobody asked for is noise; a request nobody serves is the opportunity. Falls back to your most-used hashtag when you name no niche. |
 | `detect_spoken_mentions` | 2 | **Every brand named out loud in one video.** The spoken transcript and the written caption, side by side, for your model to list each brand with its verbatim sentence, the creator's framing and whether it was said, written or both. Works where the creator never enabled captions, because the audio is transcribed. 1 credit for `get_post_transcript` plus 1 for `get_social_media`; nothing when no transcript can be made. |
 | `search_spoken_mentions` | 2 per platform narrowed by niche + 2 per creator handle + 1 per transcript, up to `maxTranscripts` | **The mirror of `search_mentions`, for what was said rather than typed.** Narrows to candidate posts (a niche sweep, named handles, and/or your watchlist), transcribes only the most-viewed survivors up to a hard ceiling, and searches the words for the term — TikTok, YouTube and Douyin, and only where the creator actually enabled captions. Reports how many candidates were found, transcribed and matched, so the spend is legible. |
@@ -159,13 +159,13 @@ a `scanId` for the rest.
 
 | Tool | Credits | What it is for |
 |------|---------|----------------|
-| `write_hooks` | 2, or free | The source post and its transcript, to write openings against. Give a topic instead of a url and it fetches nothing and costs nothing. |
-| `show_hooks` | free | Draws the hooks your model wrote from `write_hooks` — each one with the device it uses and who it stops. Makes no requests; it only renders what you pass it. |
-| `score_draft` | free | **Your** draft back with the rubric to hold it to — hook, clarity, payoff, specificity and fit, each scored 1-10, plus the three fixes worth making and a rewritten opening. Fetches nothing: the text is already yours. The only tool that runs before the content exists. |
-| `repurpose_post` | 2 | The source post and its transcript, to rewrite for other surfaces — X thread, LinkedIn post, carousel slides, YouTube metadata, newsletter. |
-| `show_repurposed_post` | free | Draws the rewritten copy your model produced from `repurpose_post` — one entry per surface. Makes no requests; it only renders what you pass it. |
-| `create_variants` | 2 | The post that worked, with its transcript, to build variants from: hook, the angle that changes, ordered shot beats and a CTA. |
-| `show_variants` | free | Draws the variants your model wrote from `create_variants` — each one's hook, angle, beats and CTA. Makes no requests; it only renders what you pass it. |
+| `generate_hook_ideas` | 2, or free | The source post and its transcript, to write openings against. Give a topic instead of a url and it fetches nothing and costs nothing. |
+| `show_hooks` | free | Draws the hooks your model wrote from `generate_hook_ideas` — each one with the device it uses and who it stops. Makes no requests; it only renders what you pass it. |
+| `evaluate_social_draft` | free | **Your** draft back with the rubric to hold it to — hook, clarity, payoff, specificity and fit, each scored 1-10, plus the three fixes worth making and a rewritten opening. Fetches nothing: the text is already yours. The only tool that runs before the content exists. |
+| `adapt_post_for_platform` | 2 | The source post and its transcript, to rewrite for other surfaces — X thread, LinkedIn post, carousel slides, YouTube metadata, newsletter. |
+| `show_repurposed_post` | free | Draws the rewritten copy your model produced from `adapt_post_for_platform` — one entry per surface. Makes no requests; it only renders what you pass it. |
+| `generate_post_variants` | 2 | The post that worked, with its transcript, to build variants from: hook, the angle that changes, ordered shot beats and a CTA. |
+| `show_variants` | free | Draws the variants your model wrote from `generate_post_variants` — each one's hook, angle, beats and CTA. Makes no requests; it only renders what you pass it. |
 
 ### Account
 
@@ -173,6 +173,8 @@ a `scanId` for the rest.
 |------|---------|----------------|
 | `nooticr_getting_started` | free | **Start here.** Where this account stands — balance, connected accounts, watchlist — and the next calls worth making, each with its price and an example. The server's `instructions` point every host at it. |
 | `check_nooticr_credits` | free | Balance and billing URL. |
+| `nooticr_settings_read` | free | Read your default social platform and result count. |
+| `nooticr_settings_update` | free | Save the default platform and result count used by supported searches when arguments are omitted. |
 | `list_tool_runs` | free | Your tool-call history: what ran, whether it worked, and the credits each call actually took (0 for a free, refunded, cached or replayed call). `scope: "workspace"` shows every member's runs to owners and admins. |
 | `get_tool_run` | free | One run from that history by id, with its full error. |
 | `get_usage_report` | free | The run ledger added up over a window: total calls, failures and credits actually taken, per tool, per day and the most recent failures. `scope: "workspace"` adds one row per seat, for the workspace's owners and admins. |
@@ -194,7 +196,7 @@ Everything above reads someone else's content. These read and generate for **you
 | `get_scheduled_posts` | free | Your own scheduled and draft posts in the content pipeline — title, status, scheduled time, approval status. What is queued to publish. |
 | `get_post_performance` | free | Your own already-published posts with their engagement counters — views, likes, comments, shares, platform, post date. The raw performance history, not an interpretation of it; pair with `growth_brief` for that. |
 | `get_video_stats` | free | Your own most recently synced video performance stats across every connected creator — views, likes, comments, shares, plus a running total. Reads the last sync; does not trigger a new one. |
-| `get_google_analytics` | free | Your product's GA4 sync **as of its last sync into nooticr, not live** — property, date range, rows synced. The metrics feed `get_post_performance` and `growth_brief`. |
+| `get_google_analytics_data` | free | Your product's GA4 sync **as of its last sync into nooticr, not live** — property, date range, rows synced. The metrics feed `get_post_performance` and `growth_brief`. |
 | `get_search_console_data` | free | Search Console clicks, impressions and top queries, as of the last sync — whether people search for what your content is about. |
 | `get_posthog_analytics` | free | Your PostHog pageview trend, as of the last sync — line a post's date up against traffic to your site. |
 | `get_content_plan` | free | The saved weekly content plan for a product, if one has been generated. `plan: null` when none has. |
@@ -280,13 +282,13 @@ Twenty frames is about 2.4% of a million-token context.
 | Tool | What comes back | Credits |
 |---|---|---|
 | `analyze_post` | frames as images, plus the transcript and stats | **3** (2 + 1) |
-| `analyze_comments` | the comments, each with an id, and the labels to use | **2** |
+| `summarize_post_comments` | the comments, each with an id, and the labels to use | **2** |
 | `analyze_creator_profile` | the creator's recent posts and their numbers | **2** |
-| `score_draft` | your own draft, and the rubric to score it against | **free** |
+| `evaluate_social_draft` | your own draft, and the rubric to score it against | **free** |
 
 The prices above are derived from the fetches each tool makes rather than
 written down twice — see `EVIDENCE_PLANS` and `planCost` in
-`src/shared/evidence.ts`. `score_draft` has no plan at all: it reviews text you
+`src/shared/evidence.ts`. `evaluate_social_draft` has no plan at all: it reviews text you
 already have, so there is nothing to fetch and nothing to charge for.
 
 `show_comment_review` closes the loop: hand back your classifications and it

package/dist/shared/amazon.js

@@ -107,7 +107,7 @@ export function normaliseProducts(raw) {
                 return {
                     // Addressable, so the model's analysis can point back at the exact
                     // review it read a driver or a barrier out of. Same shape
-                    // analyze_comments mints for a comment.
+                    // summarize_post_comments mints for a comment.
                     id: String(row.id ?? `review:${id}:${i}`),
                     asin: id,
                     brand: String(p.brand ?? ""),

package/dist/shared/comment-review.js

@@ -3,7 +3,7 @@
  *
  * ## Why
  *
- * `analyze_comments` used to fetch a comment section, send it to Gemini, and
+ * `summarize_post_comments` used to fetch a comment section, send it to Gemini, and
  * return Gemini's opinion. That cost 6 credits, took a round trip to a third
  * party, and died when that third party declined — measured: `Gemini text 403
  * Forbidden` while `get_post_comments` returned the same post's comments fine.
@@ -139,7 +139,7 @@ export function classificationBlock() {
  *
  * The view has drawn per-item category chips, a counted filter row and the
  * click-to-filter behind them for as long as they have existed — but only
- * `analyze_comments` ever handed a host the taxonomy, so on a brand sweep
+ * `summarize_post_comments` ever handed a host the taxonomy, so on a brand sweep
  * across nine networks, the most expensive call in the product, all three were
  * inert every time (#79). Nothing needed building; the host was simply never
  * asked.

package/dist/shared/evidence-digest.js

@@ -140,7 +140,7 @@ function postLine(row, b) {
 /**
  * One comment, with its id.
  *
- * The id is the load-bearing field: `analyze_comments` asks for a
+ * The id is the load-bearing field: `summarize_post_comments` asks for a
  * classification per comment and `show_comment_review` takes those ids back.
  * A digest that renders the text and drops the id breaks the next call.
  */

package/dist/shared/evidence.js

@@ -264,7 +264,7 @@ export const EVIDENCE_PLANS = {
             ownIt,
         ].join("\n"),
     },
-    compare_posts: {
+    compare_social_posts: {
         via: "get_social_media",
         args: (a) => ({ url: String(a.urls?.[0] ?? "") }),
         guidance: (a) => [
@@ -356,7 +356,7 @@ export const EVIDENCE_PLANS = {
             ownIt,
         ].join("\n"),
     },
-    write_hooks: {
+    generate_hook_ideas: {
         via: "get_social_media",
         args: (a) => ({ url: url(a) }),
         also: { via: "get_post_transcript", args: (a) => ({ url: url(a) }) },
@@ -385,7 +385,7 @@ export const EVIDENCE_PLANS = {
             ].join("\n");
         },
     },
-    create_variants: {
+    generate_post_variants: {
         via: "get_social_media",
         args: (a) => ({ url: url(a) }),
         also: { via: "get_post_transcript", args: (a) => ({ url: url(a) }) },
@@ -407,7 +407,7 @@ export const EVIDENCE_PLANS = {
             ].join("\n");
         },
     },
-    repurpose_post: {
+    adapt_post_for_platform: {
         via: "get_social_media",
         args: (a) => ({ url: url(a) }),
         also: { via: "get_post_transcript", args: (a) => ({ url: url(a) }) },
@@ -429,14 +429,14 @@ export const EVIDENCE_PLANS = {
     },
 };
 /**
- * `score_draft` has no plan, and deliberately so.
+ * `evaluate_social_draft` has no plan, and deliberately so.
  *
  * It reviews text the caller already supplied, so there is nothing to fetch:
  * a plan for it would be a paid call that handed back the caller's own input.
  * It stays on the tool list as a free tool instead — see `scoreDraftGuidance`,
  * which is the whole of what it now does.
  */
-export const FETCHES_NOTHING = ["score_draft"];
+export const FETCHES_NOTHING = ["evaluate_social_draft"];
 /**
  * What the calling model is asked to produce for a draft.
  *
@@ -447,7 +447,7 @@ export const FETCHES_NOTHING = ["score_draft"];
  *
  * The tool could have been dropped instead. It is kept because a model reading
  * a tool list treats the list as the menu of what is worth doing — with no
- * `score_draft` on it, "check this before I film it" stops being a step
+ * `evaluate_social_draft` on it, "check this before I film it" stops being a step
  * anybody takes, and the `check_my_draft` prompt loses its first move. Naming
  * the axes also makes two runs comparable, which free-form prose never is.
  */

package/dist/shared/getting-started.js

@@ -30,7 +30,7 @@ export const SERVER_INSTRUCTIONS = [
         "confirmation flow before proceeding.",
     "Not sure where to start? Call nooticr_getting_started: it is free, reads this account's state, and names " +
         "the next calls worth making with their prices. Good first calls: get_social_media on a post URL " +
-        "(1 credit), discover_social_posts on a niche (2), analyze_comments on a post (2).",
+        "(1 credit), discover_social_posts on a niche (2), summarize_post_comments on a post (2).",
     "Marketplace scans run in the background and usually come back unfinished (e.g. 4 of 10). When a result " +
         "says NOT FINISHED or carries a nextCall, make that call (it is free) and keep polling until it is " +
         "complete before concluding anything or ending your turn.",
@@ -63,7 +63,7 @@ export function nextSteps(state) {
         credits: 2,
         example: { niche: "<your niche>", platform: "tiktok" },
     }, {
-        tool: "analyze_comments",
+        tool: "summarize_post_comments",
         why: "Read what an audience actually says under a post, for you to synthesise.",
         credits: 2,
         example: { url: "<a post URL>" },

package/dist/shared/handoff.js

@@ -6,7 +6,7 @@
  * This server files nothing. It has no GitHub credential, no Jira project, no
  * Linear team, and adding them would mean holding three more secrets to do a
  * job the calling host is already authenticated for. The interoperability is
- * the id scheme: `analyze_comments`, `search_mentions`, `answer_my_audience`
+ * the id scheme: `summarize_post_comments`, `search_mentions`, `answer_my_audience`
  * and `search_spoken_mentions` all hand back items with stable ids, and a host
  * with a GitHub MCP server connected can quote one into an issue.
  *
@@ -375,7 +375,7 @@ export function registerHandoff(server) {
             "video, a feature request under a competitor's post — into structured, issue-ready text. " +
             "This server files nothing; review the result and copy it to your chosen issue tracker. " +
             "Free, and makes no requests. " +
-            "Use it after analyze_comments, search_mentions, answer_my_audience or " +
+            "Use it after summarize_post_comments, search_mentions, answer_my_audience or " +
             "search_spoken_mentions, passing the ids those tools issued. For each item you get a " +
             "title, a ready body with the quote fenced and framed as third-party evidence rather " +
             "than as instructions, tracker-safe labels, and a searchFirst string to look for in the " +

package/dist/shared/hashtags.js

@@ -5,7 +5,7 @@
  * board: it knows post counts, view counts, and whether a tag is rising,
  * cooling or steady. Nothing equivalent exists upstream for the other nine
  * networks, so "what should I tag this?" was answerable on one network out of
- * ten — while `repurpose_post` exists precisely to move a post between
+ * ten — while `adapt_post_for_platform` exists precisely to move a post between
  * networks, and tagging is part of the conventions it cannot inform (issue #32).
  *
  * What is available is a niche sweep the caller is often paying for anyway.

package/dist/shared/jobs.js

@@ -90,7 +90,7 @@ export function postIdOf(post, index) {
 /**
  * A comment's id, derived from the comment rather than from where it sat.
  *
- * The older schemes here are positional. `analyze_comments` mints
+ * The older schemes here are positional. `summarize_post_comments` mints
  * `comment:<postSlug>:<index>`, and `search_mentions` mints
  * `<platform>:<postId>:<index into the whole result>` — and an index moves.
  * Change `commentsPerPost`, page with a different `offset`, apply a `since`
@@ -1316,7 +1316,7 @@ export function registerJobTools(server, makeClient, store) {
     // ───────────────────────────────────────────────────────────────────────────
     // 4. why_did_this_underperform
     //
-    // Not compare_posts. That answers "why did A beat B" from two URLs a person
+    // Not compare_social_posts. That answers "why did A beat B" from two URLs a person
     // already suspects; this answers "is this even bad, and against what", which
     // needs the creator's own distribution rather than a second post.
     // ───────────────────────────────────────────────────────────────────────────
@@ -1328,7 +1328,7 @@ export function registerJobTools(server, makeClient, store) {
             "own baseline, and returns where it actually sits in the distribution — median, " +
             "quartiles, ratio and percentile — so the answer can be 'this is a normal result, not a " +
             "failure'. Consumes 3 nooticr credits (1 for the post, 2 for the window). Use when you " +
-            "have one post and no comparison; compare_posts is for two URLs you already picked.",
+            "have one post and no comparison; compare_social_posts is for two URLs you already picked.",
         annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
         outputSchema: OUTPUT_SCHEMAS.why_did_this_underperform,
         inputSchema: z

package/dist/shared/loading-plans.js

@@ -67,6 +67,8 @@ const CREATOR_UNIT = {
  * generic grey box that said "Working".
  */
 export const LOADING_PLANS = {
+    nooticr_settings_read: { label: "Reading your research defaults", kind: "text", n: 0, steps: [], free: true },
+    nooticr_settings_update: { label: "Saving your research defaults", kind: "text", n: 0, steps: [], free: true },
     // ─── Read a post ───
     get_social_media: { label: "Fetching the post", kind: "post", n: 1, steps: [step("get_social_media")] },
     get_post_transcript: {
@@ -98,18 +100,18 @@ export const LOADING_PLANS = {
         n: 1,
         steps: evidenceSteps("analyze_post_fast"),
     },
-    analyze_comments: {
+    summarize_post_comments: {
         label: "Reading the comment section",
         kind: "text",
         n: 1,
         // Not an evidence plan: it proxies one get_post_comments and synthesises.
         steps: [step("get_post_comments")],
     },
-    compare_posts: {
+    compare_social_posts: {
         label: "Fetching the first post",
         kind: "strip",
         n: 2,
-        steps: evidenceSteps("compare_posts"),
+        steps: evidenceSteps("compare_social_posts"),
         note: "1 credit more for every further post you fetch yourself.",
     },
     // ─── Research ───
@@ -154,21 +156,21 @@ export const LOADING_PLANS = {
     },
     niche_report: { label: "Reading the niche", kind: "text", n: 1, steps: evidenceSteps("niche_report") },
     // ─── Make something ───
-    write_hooks: { label: "Reading the source post", kind: "text", n: 1, steps: evidenceSteps("write_hooks") },
-    create_variants: {
+    generate_hook_ideas: { label: "Reading the source post", kind: "text", n: 1, steps: evidenceSteps("generate_hook_ideas") },
+    generate_post_variants: {
         label: "Reading the post that worked",
         kind: "text",
         n: 1,
-        steps: evidenceSteps("create_variants"),
+        steps: evidenceSteps("generate_post_variants"),
     },
-    repurpose_post: {
+    adapt_post_for_platform: {
         label: "Reading the source post",
         kind: "text",
         n: 1,
-        steps: evidenceSteps("repurpose_post"),
+        steps: evidenceSteps("adapt_post_for_platform"),
     },
     // Fetches nothing: the draft is already the caller's.
-    score_draft: { label: "Scoring the draft", kind: "text", n: 1, steps: [], free: true },
+    evaluate_social_draft: { label: "Scoring the draft", kind: "text", n: 1, steps: [], free: true },
     // ─── Brand monitoring ───
     search_mentions: {
         label: "Sweeping for mentions",
@@ -451,7 +453,7 @@ export const LOADING_PLANS = {
     get_scheduled_posts: { label: "Reading your pipeline", kind: "list", n: 5, steps: [], free: true },
     get_post_performance: { label: "Reading your numbers", kind: "list", n: 5, steps: [], free: true },
     get_video_stats: { label: "Reading the last sync", kind: "strip", n: 3, steps: [], free: true },
-    get_google_analytics: { label: "Reading your last GA4 sync", kind: "text", n: 1, steps: [], free: true },
+    get_google_analytics_data: { label: "Reading your last GA4 sync", kind: "text", n: 1, steps: [], free: true },
     get_search_console_data: { label: "Reading your last Search Console sync", kind: "text", n: 1, steps: [], free: true },
     get_posthog_analytics: { label: "Reading your last PostHog sync", kind: "text", n: 1, steps: [], free: true },
     get_brand_playbook: { label: "Reading the playbook", kind: "text", n: 1, steps: [], free: true },

package/dist/shared/output-schemas.js

@@ -474,7 +474,7 @@ export const OUTPUT_SCHEMAS = {
      * left optional because the schema is passthrough and a caller that stored
      * one should not find the key gone.
      */
-    analyze_comments: open({
+    summarize_post_comments: open({
         guidance,
         summary: scalar(),
         themes: anyList(),
@@ -572,7 +572,7 @@ export const OUTPUT_SCHEMAS = {
     // show_comment_review: they only draw what they're handed.
     show_compared_posts: open({
         verification: checkedAgainstSession,
-        posts: listOf(post).describe("The 2-5 posts being compared, same shape as compare_posts returned."),
+        posts: listOf(post).describe("The 2-5 posts being compared, same shape as compare_social_posts returned."),
         comparison: open({
             winner: scalar().describe("1-indexed position of the post that won, matching the posts array."),
             winnerReason: scalar(),
@@ -901,7 +901,7 @@ export const OUTPUT_SCHEMAS = {
         post: open({}).nullish(),
         evidenceFrom: listOf(z.string()),
     }),
-    compare_posts: open({
+    compare_social_posts: open({
         ...evidence,
         posts: listOf(post),
         failed: anyList(),
@@ -1033,7 +1033,7 @@ export const OUTPUT_SCHEMAS = {
         })).optional(),
         mcpCredits,
     }),
-    write_hooks: open({
+    generate_hook_ideas: open({
         ...evidence,
         hooks: listOf(open({
             hook: scalar(),
@@ -1043,7 +1043,7 @@ export const OUTPUT_SCHEMAS = {
         sourceUrl: scalar(),
         mcpCredits,
     }),
-    create_variants: open({
+    generate_post_variants: open({
         ...evidence,
         variants: listOf(open({
             hook: scalar(),
@@ -1061,13 +1061,13 @@ export const OUTPUT_SCHEMAS = {
      * the rubric and the reading is the caller's. Same rule as `provider` above:
      * documenting a field that never arrives is worse than omitting it.
      */
-    score_draft: open({
+    evaluate_social_draft: open({
         guidance,
         draft: scalar(),
         platform: scalar(),
         mcpCredits,
     }),
-    repurpose_post: open({
+    adapt_post_for_platform: open({
         ...evidence,
         repurposed: open({}).nullish().describe("One entry per target surface."),
         post: post.nullish(),
@@ -1390,7 +1390,7 @@ export const OUTPUT_SCHEMAS = {
     // The connector reads (#104). Each is the backend's connector_sync_cache
     // row as stored, plus `synced_at`, the hoisted appId/appName, and the
     // `connector` this surface adds so the view knows which table to draw.
-    get_google_analytics: open({
+    get_google_analytics_data: open({
         connector: scalar(),
         propertyId: scalar(),
         rowsSynced: scalar(),

package/dist/shared/own-account.js

@@ -383,7 +383,7 @@ export function registerOwnAccountTools(server, makeClient) {
             return failed(`${name} failed`, err);
         }
     });
-    connectorRead("get_google_analytics", "google_analytics", "Read Google Analytics Data", "Your own product's Google Analytics (GA4) sync, as of its last sync into nooticr — not a live " +
+    connectorRead("get_google_analytics_data", "google_analytics", "Read Google Analytics Data", "Your own product's Google Analytics (GA4) sync, as of its last sync into nooticr — not a live " +
         "GA4 call: the property, the date range synced and how many daily rows came in. The metrics " +
         "themselves (installs, opens, purchases, revenue) feed get_post_performance and growth_brief " +
         "rather than being repeated here. Returns a message rather than an error when nothing has " +

package/dist/shared/prompts.js

@@ -147,9 +147,9 @@ export function registerPrompts(server) {
         },
     }, ({ draft, platform }) => userMessage(`Review this draft before I film it${platform ? ` for ${platform}` : ""}:\n\n"""\n${draft}\n"""\n\n` +
         `Work in this order:\n` +
-        `1. score_draft on it — free, and it returns the draft with the rubric to score it against: ` +
+        `1. evaluate_social_draft on it — free, and it returns the draft with the rubric to score it against: ` +
         `hook, clarity, payoff, specificity and fit, plus the fixes worth making.\n` +
-        `2. write_hooks on the same topic for alternative openings to choose between.\n\n` +
+        `2. generate_hook_ideas on the same topic for alternative openings to choose between.\n\n` +
         `Then tell me plainly: is the hook doing work in the first two seconds, where does attention ` +
         `leak, and which of the alternative hooks you would actually use and why. If the draft is ` +
         `fine as it stands, say so rather than inventing changes.\n\n${COST_RULE}`));
@@ -170,7 +170,7 @@ export function registerPrompts(server) {
             ? `3. analyze_post — the visual pass, since the framing and editing are the point here.\n`
             : `3. Skip analyze_post unless the fast pass leaves the visuals genuinely unexplained. It ` +
                 `fetches frames on top of the transcript, so it costs a credit more; say so before spending it.\n`) +
-        `4. analyze_comments — what the audience actually took away, which is often not what the ` +
+        `4. summarize_post_comments — what the audience actually took away, which is often not what the ` +
         `creator intended.\n\n` +
         `Then give me: the hook and why it stops someone, the structure beat by beat, the CTA, and the ` +
         `gap (if any) between what the post says and what the comments show people heard.\n\n${COST_RULE}`));
@@ -181,7 +181,7 @@ export function registerPrompts(server) {
             urls: z.string().describe("2-5 post URLs, separated by spaces or commas."),
         },
     }, ({ urls }) => userMessage(`Compare these posts and explain the performance gap:\n${urls}\n\n` +
-        `Start with compare_posts, then fetch the remaining URLs it names with get_social_media — it ` +
+        `Start with compare_social_posts, then fetch the remaining URLs it names with get_social_media — it ` +
         `pulls the first post and leaves the comparison, which is the part you should be doing.\n\n` +
         `Then tell me: which won, what actually differed (hook, format, length, caption, tags), what ` +
         `they share that I should keep, and one concrete experiment that would test your explanation. ` +
@@ -197,9 +197,9 @@ export function registerPrompts(server) {
         },
     }, ({ url, angle }) => userMessage(`This post worked: ${url}. Tell me what to film next.\n\n` +
         `Work in this order:\n` +
-        `1. analyze_comments — the audience already said what they want more of, and the questions they ` +
+        `1. summarize_post_comments — the audience already said what they want more of, and the questions they ` +
         `asked are the cheapest content ideas available.\n` +
-        `2. create_variants${angle ? ` with the angle "${angle}"` : ""} — same mechanism, different ` +
+        `2. generate_post_variants${angle ? ` with the angle "${angle}"` : ""} — same mechanism, different ` +
         `execution, with hooks and shot beats.\n\n` +
         `Then give me a shortlist I could film this week, each with its hook, what changes versus the ` +
         `original, and which comment or pattern it is answering. Order them by how much evidence there ` +
@@ -217,7 +217,7 @@ export function registerPrompts(server) {
         },
     }, ({ url, targets }) => userMessage(`Repurpose this post for other surfaces: ${url}\n` +
         (targets ? `Targets: ${targets}\n` : "") +
-        `\nUse repurpose_post. If the post's argument depends on the exact wording, pull ` +
+        `\nUse adapt_post_for_platform. If the post's argument depends on the exact wording, pull ` +
         `get_post_transcript first so the rewrite carries the real lines rather than a summary of them.\n\n` +
         `Then give me each version ready to paste, and note for each one what you changed about the ` +
         `shape and why that surface rewards it.\n\n${COST_RULE}`));

package/dist/shared/settings.js

@@ -0,0 +1,69 @@
+export const SETTINGS_READ_TOOL = "nooticr_settings_read";
+export const SETTINGS_UPDATE_TOOL = "nooticr_settings_update";
+export const DEFAULT_SOCIAL_PLATFORMS = [
+    "tiktok",
+    "instagram",
+    "youtube",
+    "twitter",
+    "reddit",
+    "douyin",
+    "xiaohongshu",
+    "weibo",
+    "bilibili",
+];
+export const DEFAULT_NOOTICR_SETTINGS = {
+    defaultSocialPlatform: "tiktok",
+    // Keep existing tool behaviour until the user chooses another count.
+    defaultResultCount: 12,
+};
+export class MemorySettingsStore {
+    values = new Map();
+    async get(owner) {
+        const value = this.values.get(owner);
+        return value ? { ...value } : undefined;
+    }
+    async put(owner, value) {
+        this.values.set(owner, { ...value });
+    }
+}
+/** Durable account-scoped preferences for the Cloudflare-hosted MCP server. */
+export class KvSettingsStore {
+    kv;
+    constructor(kv) {
+        this.kv = kv;
+    }
+    key(owner) {
+        return `plugin-settings:${owner}`;
+    }
+    async get(owner) {
+        const raw = await this.kv.get(this.key(owner));
+        if (!raw)
+            return undefined;
+        try {
+            const parsed = JSON.parse(raw);
+            const platform = DEFAULT_SOCIAL_PLATFORMS.find((candidate) => candidate === parsed.defaultSocialPlatform);
+            const count = parsed.defaultResultCount;
+            if (!platform || !Number.isInteger(count) || count < 3 || count > 12)
+                return undefined;
+            return { defaultSocialPlatform: platform, defaultResultCount: count };
+        }
+        catch {
+            return undefined;
+        }
+    }
+    async put(owner, value) {
+        await this.kv.put(this.key(owner), JSON.stringify(value));
+    }
+}
+/** Stable owner keys prefer the authenticated Nooticr account ID. */
+export async function settingsOwnerFromAuth(authInfo, resolveAccountId) {
+    const token = authInfo?.token ?? "";
+    const accountId = token && resolveAccountId ? await resolveAccountId(token) : undefined;
+    if (accountId)
+        return `account:${accountId}`;
+    if (!token)
+        return "local";
+    const digest = await crypto.subtle.digest("SHA-256", new TextEncoder().encode(token));
+    const hex = Array.from(new Uint8Array(digest), (byte) => byte.toString(16).padStart(2, "0")).join("");
+    return `credential:${hex}`;
+}

package/dist/shared/tasks.js

@@ -5,7 +5,7 @@
  * chosen — including the ones that watch a video. POLL_TIMEOUT_MS is five
  * minutes, so analyze_post could hold a synchronous tools/call open for that
  * long and a host had no way to put it in the background. Measured against the
- * live server, discover_social_posts takes 10.3s and compare_posts 10.4s; the
+ * live server, discover_social_posts takes 10.3s and compare_social_posts 10.4s; the
  * multimodal tools wrapped here are the slow ones above them.
  *
  * The three tools that run longest now accept a task. What they do is