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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/closermethod/content-hooks-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server