List the user's Twitter BOOKMARKS — posts they deliberately saved. Never includes X Likes; use list_likes for those. Supports filtering and pagination. Supports filtering by read status, media type, author, tags, date ranges, and sorting options. IMPORTANT: Use this tool (with the 'author' parameter) when the user asks to show tweets by a specific author.
輸入參數taglimitauthorcursorsort_byposted_tomedia_typeposted_fromsort_cursorbookmarked_tohide_archivedis_unread_only另有 1 個
List the posts the user LIKED on X (not their bookmarks). Likes are a lighter signal than a save — use list_bookmarks for things the user deliberately saved, and this when the user explicitly asks about likes or about what they react to. Same filters and pagination as list_bookmarks.
輸入參數taglimitauthorcursorsort_byposted_tomedia_typeposted_fromsort_cursorbookmarked_tohide_archivedis_unread_only另有 1 個
Search through a user's Twitter bookmarks using keyword search (q), semantic search (vector_search_term), or author filtering (author). At least one of q, vector_search_term, or author should be provided. IMPORTANT: Use the 'author' parameter for filtering by author, not the 'q' field.
輸入參數qtaglimitauthorcursorsort_byposted_tomedia_typeposted_fromsort_cursorbookmarked_tohide_archived另有 3 個
Get the total count of user's bookmarks with optional filtering. Useful for understanding the size of bookmark collections before listing them.
輸入參數tagauthorposted_tomedia_typeposted_frombookmarked_tohide_archivedis_unread_onlybookmarked_from
List all user's labels with their usage counts. Useful for discovering existing labels before adding new ones.
無需輸入參數。
Delete a label from the account entirely — the label itself plus every bookmark's assignment of it. The BOOKMARKS are not deleted; they simply lose this label. IRREVERSIBLE: before calling, tell the user how many bookmarks carry the label (list_labels returns the count) and get an explicit yes. To take a label off SOME bookmarks instead, use remove_labels_from_tweets. If the name matches more than one label the call fails with the candidates — re-run with label_id.
輸入參數label_idlabel_name
Initialize the vector store for semantic bookmark search. CRITICAL: When vector/semantic search fails with 'Vector Store Not Setup' error, call this tool. This is an async operation that may take a few minutes for large bookmark collections.
無需輸入參數。
START HERE for any open-ended request. Lists the task playbooks this server supports — systematic learning from bookmarks, organising into themes, cleaning up, X-list intelligence, exporting data out, finding a half-remembered save, digests, and diagnosing sync. Each names when to use it; call get_skill for the exact tool sequence.
無需輸入參數。
Get the full playbook for a task: when to use it, the exact tool sequence with the arguments that matter, tips, and the pitfalls that cause empty results. `name` takes EITHER an exact skill name (learn_from_bookmarks, organise_into_themes, cleanup_library, list_intelligence, get_my_data_out, find_that_thing, stay_on_top, diagnose_sync, connect_your_tool) OR a plain description of the job — both resolve. You do NOT need list_skills first: if you already know what the user is trying to do, call this directly with their request and skip the round trip. Reach for list_skills only to browse what exists.
輸入參數name
A snapshot of the whole library: total bookmarks, unread, untagged, breakdown by type (threads/media/links/notes), every label with its count, and the years covered. Use this FIRST for anything open-ended (organise, clean up, learn from my saves, 'how many do I have per topic') instead of paging through bookmarks.
無需輸入參數。
Answer questions about Tweetsmash itself — features, how-to, pricing, plans, limits, account/subscription. Searches the bundled product guide and returns the most relevant sections for you to answer from. Call with an empty query to list the help topics.
輸入參數query
Get a single saved bookmark with FULL content in one call — the full X Article body, the unrolled thread, notes, and (optionally) replies. Use `include` (comma list of article,thread,notes,replies) to narrow it; defaults to article,thread,notes. Use this when the user wants to read or summarize a specific saved tweet/thread/article in depth.
輸入參數id必填include
Add a label to EVERY bookmark matching a filter, in a single call. Prefer this over listing then looping when the user says 'tag all my … as …'. Resolves an author name to its id automatically. Reports matched/tagged/failed counts.
輸入參數qtagauthorlabel_idposted_tolabel_namemedia_typeposted_frombookmarked_tohide_archivedis_unread_onlybookmarked_from
Archive, unarchive, delete, undelete, or mark read/unread a list of bookmarks by id (max 500). This is a bulk write; for destructive actions (delete) confirm with the user first. Reports how many changed.
輸入參數action必填tweet_ids必填
archive_bookmarks_by_filter
Apply archive/unarchive/delete/undelete to EVERY bookmark matching a filter, in one call. Destructive by nature — confirm with the user before delete. Reports counts.
輸入參數tagsvalueaction必填filtersearch_query
List the user's Smart Views (saved filtered views). Each has a slug you pass to the other smart-view tools.
無需輸入參數。
Get a single Smart View by slug (its filter, tabs/buckets, and sort).
輸入參數slug必填
List the bookmarks inside a Smart View, optionally scoped to one tab/bucket. Use the returned ids with archive_bookmarks / tagging tools to act on the view.
輸入參數slug必填limitbucketcursor
Create a Smart View from a filter so the user can reuse it. Provide a name and the base_query (filter).
輸入參數name必填base_querydescriptiondefault_sorttriage_buckets
Update a Smart View (name, filter, tabs, sort) by slug.
輸入參數nameslug必填base_querydescriptiondefault_sorttriage_buckets
Delete a Smart View by slug.
輸入參數slug必填
Create a public, read-only share link for a set of bookmarks (explicit ids or everything matching a filter). Returns a share_url valid for 7 days. Free plans share up to 10 bookmarks.
輸入參數tagsvaluefiltertweet_idssearch_query
Revoke a previously created share link by its token.
輸入參數token必填
Start a PDF export of the user's bookmarks (explicit ids, everything matching a filter, or the whole library). Returns a job id; tell the user the file will appear in the Export Center.
輸入參數tagsvaluefiltertweet_idssearch_query
Start a CSV export (explicit ids, a filter, or the whole library). Returns a job id; the file appears in the Export Center.
輸入參數tagsvaluefiltertweet_idssearch_query
Start a JSON export (explicit ids, a filter, or the whole library). Returns a job id; the file appears in the Export Center.
輸入參數tagsvaluefiltertweet_idssearch_query
List the user's email-digest schedules (frequency, time, paused state) for bookmark and Smart View digests.
無需輸入參數。
Update a digest schedule (enable/pause, frequency, time) by id.
輸入參數id必填is_pausedweek_infois_enabledtime_to_readschedule_timesend_frequency
Remove a digest schedule by id.
輸入參數id必填
List past digests sent to the user's email, newest first. This is Digest 1.0 (the cluster pipeline). For the AI-composed Digest 2.0, use list_mash_digests.
無需輸入參數。
The user's Mash Digest 2.0 digests — the AI-composed ones. An account can have SEVERAL (a morning read and an evening skim are two digests, not two sections of one), so START HERE and use the returned `id` for the other digest tools. Returns each digest's name, where its sections read from, and its schedule.
無需輸入參數。
Past issues of the user's Digest 2.0, newest first — what arrived and when. Deliberately WITHOUT the content: pick one and call get_mash_digest_issue for the whole thing. Pass digest_id to narrow to one digest.
輸入參數limitdigest_id
One digest issue in full: its title, intro, every section, and per item the summary, why it was picked and why it matters to this user. Use it to answer 'what was in my digest?', 'why was this in there?' or to carry on a conversation about something the user just read. Items carry tweet IDS, not post text — resolve them with get_bookmark if the user asks about a specific post.
輸入參數issue_id必填
Compose one of the user's Digest 2.0 digests NOW rather than waiting for its schedule. SPENDS A DIGEST CREDIT and takes about a minute, so only call it when the user asks for a fresh digest — not to inspect the current one (use get_mash_digest_issue for that). Returns an issue_id to read back once composing finishes.
輸入參數digest_id必填
Show the user's app-sync integrations (Notion, Google Sheets, Zotero): whether each is connected/enabled, synced vs pending counts, and any errors.
無需輸入參數。
Show whether a specific bookmark has synced to a given integration connection.
輸入參數tweet_id必填connect_id必填
List past Twitter-list email digests for the user.
無需輸入參數。
Build and email a digest of a Twitter list's high-signal tweets to the user now.
輸入參數list_idconnect_id必填
Rank a followed X list exactly the way the digest ranker would, WITHOUT sending anything, and show the work: each unit carries its rank_signals (lane_fit = matches what the user builds/studies, affinity = an author they trust, engagement, substance, noise demotions) plus author groups (`group_size` + `related_items` = several posts by one author, best one leading). Use this to answer 'what's worth reading in my list?', 'why was this picked?', or to check how a preference change would land. `meta.inert_dimensions` names signals that had no data for this pool.
輸入參數sortlimitlist_idconnect_id必填window_days
The user's stated author preferences for list digests: `boost` = never-miss authors, `hide` = muted authors.
無需輸入參數。
Remember how the user feels about an author in their list digests. action=boost → never miss this author's posts (they will always be included, low-signal ones collapsed rather than dropped); action=hide → mute them; action=clear → forget the preference. Use when the user says things like 'don't let me miss marclou's updates' or 'stop showing me X'. Takes effect from the next digest and in preview_list_ranking immediately.
輸入參數action必填handle必填
Get the current user's account: identity, current plan and status, and usage (e.g. AI chat credits). Use this to answer 'who am I' / 'what plan am I on'.
無需輸入參數。
Check whether the user's tweets can be pulled: the X (Twitter) API connection (connected / disconnected), whether the browser extension has synced recently, and a rolled-up can_pull + how (x_api or extension). Use this before a sync, or when the user asks why bookmarks aren't updating. Note: the extension is browser-only and can't be driven by an agent.
無需輸入參數。
Force-pull the user's most recent bookmarks from the X API now (server-side). Requires a connected X account; if the account only syncs via the browser extension, this reports that a browser sync is needed. Use when the user asks to refresh / fetch their latest saves. For Twitter-list freshness, use get_list_tweets instead.
輸入參數maxforce
Save a durable PREFERENCE about how this user wants their bookmark library handled — the themes they organise by, topics to exclude, preferred summary length/format, which account is their main one. It carries across sessions AND into the Tweetsmash web app, which your own client memory cannot reach. Use it for lasting preferences the user states or confirms, not for general chat context, task state, or anything secret.
輸入參數key必填kind必填modevalue必填
Read back the user's saved library preferences (optionally filtered by a substring). Worth calling before an open-ended organise, summarise or cleanup task so you follow how they already like things done.
輸入參數query
Delete a saved library preference by key (optionally narrowed by kind). Use when the user changes their mind or asks you to drop something.
輸入參數keykind
Read what this user is actually interested in, inferred from their saved bookmarks, hand labels, questions and digest clicks — not from anything they typed. Returns topics with a 0-1 strength, whether each is active this week, and a `coverage` field saying how much evidence exists (`lite` means a new account: treat it as a first guess and check before relying on it). Use it to prioritise, filter or explain — then confirm with the user rather than asserting it back as fact. Evidence itself is not returned.
無需輸入參數。
Record the user's correction to an inferred interest, using a key from get_interests. Corrections are sticky — they survive every future recompute. Use `confirm` when they agree, `rename` for their own wording, `hide` to stop using an interest while keeping its history, `boost` when they want it weighted higher. `forget` is different and IRREVERSIBLE: it erases the underlying history so the topic cannot re-form — only use it when the user clearly asks to delete, and say what it means first.
輸入參數valueaction必填interest_key必填