UserClimb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
UserClimb helps you write social content (ideas, hooks, reel scripts, carousels, captions) for someone's app, SaaS or product the way a good human marketer would, instead of the generic way AI usually does.
Whenever you write content ideas, hooks, scripts, carousels or captions to market a product, work in this order:
find_app_type with a description of the product, then get_playbook for that type. Read who the viewer is, the words they use, what stops them and what flops.
Follow the method (writing_method): one person in one moment, their own words, the tension between what they want and what's in the way, go wide then cut hard, specific beats clever, one idea per post, pay it off then ask.
For hooks use get_hooks; for reel scripts use get_video_structures; for carousels use get_playbook with section "carousels".
Run check_draft on what you write and fix what it flags before showing it. Never invent reviews, results, numbers or people: use [fill-ins] for anything the founder has to supply. No em dashes.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| writing_methodA | Why AI content sounds robotic and the step-by-step method a good human marketer follows instead, plus the rules and the words that give AI away. Read this before writing any content ideas, hooks, scripts, carousels or captions. |
| find_app_typeA | Matches a product to one of 12 app type playbooks (habits, fitness, money, style, utilities, social and dating, learning, games, founder and dev tools, creator and business tools, family and pets, marketplaces). Pass a plain description of what the product does and who it's for. |
| get_playbookA | The marketing playbook for one kind of app, written from research into real accounts that grew apps like it with short-form video. Sections: overview (who watches, their words, what stops them, content pillars, what to keep out), audience, reels (pillars, ways to make them, hooks, worked examples), hooks, cta, carousels (slide-by-slide shapes), platforms (and real accounts to study), examples (strong vs weak), or all. |
| get_hooksB | Hook rules and patterns with [fill-ins]: what works for any app, plus the angles (pains, desires, everyday moments), patterns that work and patterns that flop for one kind of app. Use them as shapes, never word for word. |
| get_video_structuresA | Proven structures for short videos (Reels, TikToks, Shorts), each with its hook pattern, the shape beat by beat, what it earns (watch time, sends, saves or comments) and the ask that fits. Pass an app type to rank them for that kind of app. Includes the engagement rules. |
| get_growth_movesC | Ways to get users beyond posting content: communities and conversations, direct outreach, creators and partnerships, launch and discovery, app store growth, referrals, and offline ideas. |
| check_draftA | Scores a hook, script, caption or carousel out of 100 for how human it reads and lists what to fix: AI-sounding words, em dashes, generic openers, the app's name in the hook, nothing specific, even sentence rhythm, no ask, and more. Instant and local. Run it on everything before showing it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| content_ideas | 10 post ideas that sound like a person, from the playbook for your kind of app. |
| hooks | 20 hooks, cut down to the 5 that only work for your viewer. |
| reel_script | One short video script: hook, beats, on-screen text and the ask. |
| carousel | A 7 to 9 slide carousel with open loops slide to slide. |
| week_plan | Seven days of posts in the right mix, plus one growth move. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| writing-method | Pick one person, in one moment, Steal their words, Find the tension, Go wide, then cut hard, Specific beats clever, One idea per post, Pay it off, then ask, Read it out loud |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: scoring drafts, explaining writing methodology, classifying app types, retrieving playbooks, hooks, video structures, and growth moves. Overlap between writing_method and get_hooks exists but is well-clarified by descriptions, with one being general principles and the other hook-specific patterns.
Most tools follow a clear verb_noun pattern (check_draft, find_app_type, get_playbook, get_hooks, get_video_structures, get_growth_moves). writing_method is the only noun-only exception, which is a minor deviation but still readable.
Seven tools are well-scoped for a focused content-marketing assistant. Each tool earns its place and no tool feels redundant or missing from the core workflow.
The surface covers the full content lifecycle from app classification and playbooks to hooks, video structures, growth moves, and draft scoring. Minor gaps exist, such as no dedicated tool for generating content ideas or calendar planning, but agents can work around them using the playbooks and hooks.