Content Hooks MCP
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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hook_mechanicsA | Get the 10 hook styles as fill-in structures with why each works, its failure mode, and what content type it fits. Styles: contrarian, specific_number, curiosity_gap, confession, stop_doing, pattern_interrupt, story_open, question_hook, future_pace, bold_claim. Optionally filter to one style. |
| audit_hookA | Audit a hook line: length vs the 2-second window, greeting openers, hype words vs receipts, specificity check, and detected style. Returns PASS/NEEDS WORK with named issues. |
| get_script_structureA | Get the beat-by-beat script structure with timings for a format: talking_head, voiceover_broll, tutorial, storytime, ugc_ad. Each includes rules that keep the format working. |
| audit_scriptA | Audit a full short-form script: hook quality, spoken length, single-CTA rule, hype vs receipts, zero-numbers check. Returns verdict with the hook sub-audit and format beats for comparison. |
| get_retention_mechanicsA | The 6 retention mechanics (open loops, payoff scheduling, pattern breaks, direct address, specificity ladder, loop endings) with how to apply each and its failure risk. |
| get_cta_rulesA | CTA rules by goal: follow, comment_seed, lead_magnet, product, save_share. Each with the rule, placement, and the one-CTA-per-video law. |
| get_full_packA | The complete content-mechanics library in one payload: hook styles, script formats, retention mechanics, CTA playbook. For full agent context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of content creation: hooks, script structure, retention, CTA rules, and audits. The full_pack tool provides a combined reference but does not overlap functionally, as it aggregates all reference materials for convenience.
Tool names follow a clear verb_noun pattern: get_ for retrieving reference materials and audit_ for analyzing content. The pattern is consistent and predictable, making it easy to infer tool purpose from the name.
Seven tools cover the core content-mechanics domain without bloat. Each tool serves a distinct educational or analytical function, and the count is well within the ideal range for a focused server.
The tool surface covers all major pillars of short-form content mechanics: hooks, script structures, retention, CTA rules, and audits. The full_pack provides a comprehensive reference, leaving no obvious gaps for the stated purpose.