Uploadcare (BYOK)
Read your Uploadcare project's uploaded files, file groups, tags and metadata with BYOK API keys
Why short-video hooks and retention structures actually work, grounded in attention psychology
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
hook_type_infolist_hook_typesretention_structure_infolist_retention_structuresfirst_3_seconds_checklistrecommend_hookcommon_mistakeshook_glossarysearch_referenceHookline is a fully local short-video hook & retention-structure reference. hook_type_info explains one opening-hook technique — curiosity gap, bold/contrarian claim, visual pattern interrupt, direct callout, problem-agitate, in medias res, countdown tease, controversial take, relatable moment, credential stack — with an example, the psychology behind why it works, and its common failure mode; list_hook_types browses all 10. retention_structure_info explains one whole-video structure — open loop, loop/callback ending, escalating stakes, three-act micro-structure, before-after-bridge, problem-solution-proof, cliffhanger segmenting, rule-of-three reveal — the same way; list_retention_structures browses all 8. first_3_seconds_checklist gives a practical opening checklist. recommend_hook suggests fitting hooks and structures for a stated content goal (tutorial, story, product demo, listicle, controversial opinion, comedy, transformation, series). common_mistakes lists frequent retention mistakes with why each hurts. hook_glossary defines core metrics (retention rate, watch time, drop-off point, loop rate, completion rate, the Zeigarnik effect, pattern interrupt, open loop). search_reference keyword-searches everything. Keyless; fully local; zero upstream calls; nothing stored.
Sources: Original synthesis grounded in established, named attention-psychology concepts (curiosity-gap theory, the Zeigarnik effect, novelty/habituation, loss aversion, source-credibility bias); hand-curated, not scraped from any single source; fully local, zero upstream calls
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://hookline.connectorbay.com/mcpRead your Uploadcare project's uploaded files, file groups, tags and metadata with BYOK API keys
Read your ImageKit media library files, versions, metadata, custom fields, URL endpoints and usage with BYOK
Read your Wistia videos, folders, tags, channels, webinars and viewing statistics with BYOK
Search Pexels free stock photos and videos, browse curated and popular media and read collections with BYOK
Genuine thumbnail/title craft principles, title patterns, and a clickbait-vs-curiosity checker
Color-grading terms, creative looks with the color-theory reasoning behind each, and how LUTs work
"Why does the curiosity-gap hook actually work?", "what's an open loop retention structure?", "best hook for a tutorial video?" — a reference that explains the mechanism behind short-form video hooks, not just a list of templates to copy.
hook_type_info explains one first-seconds hook technique — curiosity gap, bold/contrarian claim, visual pattern
interrupt, direct callout, problem-agitate, in medias res, countdown tease, controversial take, relatable moment,
credential stack — with a concrete example, the attention-psychology principle behind why it works, and its
common failure mode (list_hook_types browses all 10). retention_structure_info explains one whole-video
structure for holding attention across a full short-form video — open loop, loop/callback ending, escalating
stakes, three-act micro-structure, before-after-bridge, problem-solution-proof, cliffhanger segmenting,
rule-of-three reveal — the same way (list_retention_structures browses all 8). first_3_seconds_checklist
gives a practical checklist for a video's opening. recommend_hook suggests fitting hooks and structures for a
stated content goal. common_mistakes lists frequent hook/retention mistakes with why each one hurts.
hook_glossary defines core metrics and concepts: retention rate, average view duration, drop-off point, watch
time, loop rate, completion rate, hook, pattern interrupt, open loop, and the Zeigarnik effect. search_reference
keyword-searches every hook type and structure at once.
Not a guarantee of performance — audience, platform, execution and topic all still matter enormously, and no hook technique overrides weak content. Every "why it works" explanation is original synthesis grounded in named, established attention-psychology concepts (curiosity-gap theory, the Zeigarnik effect, novelty and habituation, loss aversion, source-credibility bias) rather than scraped marketing copy — it's meant to build real understanding of the mechanism, not just hand over a template to fill in.
Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Hookline is. Hookline is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated short-video hook and retention-structure reference, with original explanations of the attention-psychology principles behind each technique. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup or calculation.
What we receive. The arguments of each tool call — a hook-type name, a retention-structure name, a content goal, or a search keyword — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.
Everything is answered from bundled reference data and/or local computation, and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.
What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.
Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).
Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.
Children. Hookline is a general-audience service operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Effective 25 September 2026. These terms govern use of the Hookline connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://hookline.connectorbay.com/mcphttps://hookline.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Video Hooks never asks for them.