See which posts, links and releases bring visits, signups and revenue, and draft the next posts.
Scored across 18 tools
Each tool has a described, distinct purpose, and write tools (write_post vs edit_post, plan_post vs link_post_move vs update_move) are clearly separated. The main softness is among read tools — overview, data, calendar, posts, get_post and ideas all return project content, and the 'data' tool is a 14-slice catch-all that partially overlaps overview (top sources, weekly reports). Descriptions do resolve most of this, so a careful agent can pick correctly.
All tools share the uptake_ prefix and follow a readable convention: noun-only names for reads (overview, data, calendar, posts, ideas, projects) and verb_noun for actions (create_link, plan_post, write_post, dismiss_idea). Deviations are minor (ideas vs more_ideas, setup_status), not chaotic.
At 18 tools the set sits just above the comfortable 3-15 range, but the domain genuinely spans analytics, content drafting, calendar planning, move tracking and tracking diagnostics, so nearly every tool maps to a real operation. No obvious filler tools.
The surface covers the full loop: discover projects, read overview/data, generate and write posts, edit, plan in calendar, create tracked links, log outside actions, manage moves, and verify tracking. Gaps are minor — no way to delete or archive a post/idea once created, and no project creation — but these are workaroundable.
Adds a move of the maker's own to this week's list.
Inputs: title (required), why, network, project.
One week of the calendar: what was published and what it brought, scheduled posts, posts planned for a day (editorial date), and what is left to plan (moments, this week's moves, ideas).
Inputs: week, project.
Creates a tracked link that tells upTake which visits, signups and payments came from where it is shared.
Inputs: network (required), destination (required), place, project.
One slice of project data, when the overview is not enough. Slices: channels_90d (visits, signups, revenue and number of posts per source over 90 days); posts_30d (posts of the last 30 days with the visits, signups and revenue each brought); releases_30d (shipped releases and merged changes of the last 30 days (ids usable in uptake_write_post), with their drafts); revenue_by_day_30d (revenue and number of payments per day over 30 days); moments (communication moments: upcoming (ids usable in uptake_write_post), done and skipped); reports_4w (summaries of the last 4 weekly reports and their moves); mentions_7d (what people said about the product in the last 7 days); scheduled_7d (posts scheduled for the next 7 days); time_by_channel_30d (time the maker spent per network over 30 days); google_search_28d (Google Search clicks, impressions and top queries over 28 days); places_28d (results per named place (subreddit, newsletter issue) over 28 days); pages_30d (landing pages over 30 days: sessions that entered the site on each page, signups of those visitors and their signup rate (small_sample under 50 sessions)).
Inputs: slice (required), project.
Removes an idea that does not fit, with a reason; upTake will not suggest it again.
Inputs: reason (required), idea_id (required), project.
Replaces the text of one network's version of a post with the maker's own edit, like typing in upTake's Write studio. Free: no AI, no quota. Refused for a version already published or scheduled, and when the new text drops the tracked link. To rewrite with AI, use uptake_write_post.
Inputs: text (required), network (required), post_id (required), project.
One post by its id: the current version for each of its networks, whether it is posted, and whether it carries a tracked link.
Inputs: post_id (required), project.
Open post ideas (title, angle, network). Write one with uptake_write_post, about: [{kind: "idea", id}].
Inputs: project.
Makes a post count for an open move of this week: publishing the post completes the move.
Inputs: move_id (required), post_id (required), project.
Adds an action the maker did outside upTake (a post, a newsletter, a talk) to the journal, so upTake measures what it brought.
Inputs: title (required), network (required), date, project.
Asks upTake for a new series of post ideas from the project's data. Counts against the maker's monthly idea series.
Inputs: project.
The project at a glance: product, stage and goal, this week's visits, signups, paying customers and revenue against the 4 previous weeks (small_sample when a % change rests on too little data), top sources over 30 days, last actions and what they brought (tracked_link: false means estimated numbers), this week's moves, the next communication moment, the last weekly report. Empty fields say what to set up and where. Start here.
Inputs: project.
Sets or clears the day a post is planned for in the calendar. Only the editorial date: nothing is scheduled or sent.
Inputs: day (required), post_id (required), project.
Posts prepared in upTake's Write studio, with their state (Draft, Planned, Scheduled, Published…), networks and link to open them.
Inputs: filter, project.
The maker's projects (id, name, site). Every other tool takes project: call this first when the maker has several.
Inputs: no named parameters.
Checks that tracking works before reading a 0: is the website script receiving visits, do signups and payments reach upTake, do posts carry tracked links, and is the weekly report being sent. Each check says ok, warn or missing, why, and where to fix it.
Inputs: project.
Marks one of this week's moves as done (or reopens it), edits its title or reason, or dismisses it with a reason. Only when the maker asks.
Inputs: change (required), move_id (required), why, note, +3 more.
Prepares a post in upTake's Write studio, in the maker's voice and with tracked links, and returns the text for each network. Nothing is published or scheduled: the maker reviews and sends it from upTake. Counts against the maker's monthly drafts (a rewrite when the network already has a version). Takes up to a minute.
Inputs: request (required), about, post_id, project, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
SEO, competitor and AI-search data, plus blog management — draft, schedule and publish posts.
Plan SEO keywords, write and publish articles to your site, read Search Console and backlink data
Draft, schedule, and analyze content for Substack, Medium, LinkedIn, X, Bluesky, and Threads.
Plan, write and publish SEO articles on your own site, and track your Google and AI search traffic.
Add one secure layer between your agents and this server.
