Set up your channel project: voice guide, CTA block, brand, and past descriptions
A Juma Project is a shared space where the team stores everything Juma needs to know about a channel. Create one project per channel (or per client, if the agency manages multiple), add context as the team learns more, and Juma uses what's relevant every time a flow runs. For descriptions, this is what keeps the CTA block consistent across hundreds of videos and the tone aligned to the channel's existing voice.
What to add
Channel Voice Guide
How the channel sounds: formal or conversational, slang or buttoned-up, short paragraphs or long. With this in the project, descriptions come back in the channel's tone instead of a generic YouTube voice.
CTA / Link Block
The standard subscribe text, sponsor and affiliate links, lead magnet URLs, and social handles the team appends to every description. With this in the project, Juma drops it in verbatim, so the CTA block stays consistent across every video the team publishes.
Past Descriptions
Three to five descriptions from videos the team is proud of. Juma uses them to match the channel's structural conventions: how the hook is phrased, whether chapters use emoji prefixes or plain text, what hashtags consistently appear, where CTAs sit relative to the summary.
Brand Guidelines
Voice, banned phrases, hashtag conventions, naming for product features. Keeps every description aligned to brand standards without manual review for every release.
Guide Juma with project info
Add a short description to each knowledge item in the project's info field so Juma knows what each file contains and when to use it. For example:
- Channel Voice Guide: "Apply on every description. Match the channel's tone exactly."
- CTA / Link Block: "Drop into the description verbatim. Update this file when subscribe text or sponsor links change."
- Past Descriptions: "Reference set for structural conventions. Match the rhythm, not the literal copy."
- Brand Guidelines: "Apply on every release. Use the words in the USE list and avoid the words in the AVOID list."
Ship a complete YouTube description in one session
Frequently Asked Questions
How does Juma auto-extract chapters from a YouTube video?
Juma reads the video transcript along with the embedded timestamps and detects natural content shifts: topic changes, speaker transitions, scene cuts that map to a new section. Each shift becomes a chapter marker, and the chapter title is a three to seven word summary of what that segment covers. The output is ready to paste into the video's description on YouTube.
For chapters to render on YouTube, the description must start with a 0:00 timestamp and contain at least three chapter markers spaced at least ten seconds apart. Juma follows that format by default. For very short videos (under 90 seconds) where chapters aren't useful, Juma flags that the chapter block can be omitted and writes a cleaner short-form description instead.
What does the full description Juma produces include?
A full description covers six components: a hook line written to stop the scroll, an 80 to 100 word summary that previews the video's value, timestamped chapters auto-extracted from the transcript, a CTA block with subscribe text and key links, a hashtag set balanced between broad and niche, and an optional tag suggestion list for YouTube Studio's separate tags field.
The hook is anchored to a striking moment in the video when the dialogue supports it, or to the announcement's framing when the video is cinematic and music-led. The summary previews what viewers will see without giving away the payoff. The CTA block is dropped in verbatim from the channel project when one is set up, so it stays consistent across every video the team publishes.
Can Juma match the channel's existing description style?
Yes, when the team adds a Channel Voice Guide and three to five past descriptions to the project. With those in place, the new description matches the structural conventions the channel has already established: how the hook is phrased, whether chapters use emoji prefixes or plain text, where the CTA block sits relative to the summary, and what hashtags consistently appear.
Without past descriptions in the project, Juma defaults to a clean YouTube format: hook, summary, chapters in plain text with timestamps, CTA block, hashtags. That's fine for channels still establishing voice. For channels with consistent existing conventions, loading the past descriptions is what changes generic output into channel-native output.
Does Juma's chapter extraction work on long-form videos and podcasts?
Yes. For long-form videos (30 minutes and up) and podcast episodes uploaded to YouTube, chapter extraction is more useful, not less. The transcript is denser, the content shifts are clearer, and viewers rely on chapters more heavily to navigate the runtime.
For videos over an hour, Juma typically returns eight to fifteen chapters depending on how the conversation is structured. For shorter clips and product demos, three to six chapters is normal. The chapter titles stay descriptive of the segment rather than teaserish, because chapter titles serve navigation, not click-through. If the team wants more curiosity-driven chapter titles for a specific video, they can ask in the prompt and Juma adjusts.
Will the description respect YouTube character limits and SEO best practices?
Yes. YouTube allows up to 5,000 characters in the description, but only the first 100 to 150 characters appear above the "Show more" fold on most viewers' screens. Juma puts the hook line and the primary keyword in the first 100 characters so the visible-by-default copy carries weight. The full description stays well under the 5,000 character limit even with chapters, CTAs, and hashtags included.
SEO best practices are handled implicitly: the primary keyword appears in the first sentence and again in the summary, hashtags include the keyword as one of the tagged entities, and the chapter titles avoid keyword stuffing while still being descriptive. Human review on every output: the team adjusts the keyword targeting and CTA block based on the channel's strategy.