Diverge

Create a new, empty Diverge persona (seeded with the default section configuration, no content). Optional 'name' (defaults to 'Untitled') and 'persona_type'. Returns the new persona's slug to use with the other tools. Max 5 personas per user.

create_persona

Get the field schema for a section type: each writable field's name, type, whether it's required, allowed choices, and example shapes for structured JSON fields (achievements, links, location, etc.). Call this before add_item/update_item to build records correctly without guessing the format.

describe_section

Get a download LINK for the persona's LATEST resume PDF. The link renders the current profile fresh on open (so it always reflects edits made this session), needs no sign-in, and expires after a while. Give the URL to the user to download. Omit persona_slug to use the default persona. Optional 'label' tags the download for analytics (e.g. 'acme-hr', 'linkedin').

download_resume

Resume analytics for a persona over the last N days: download counts (overall and by tag), link clicks broken down by section, channel tag, country and device, human-vs-bot, and top links. Omit persona_slug for the default persona. Optional 'days' (default 30) and 'label' to filter to one channel tag.

get_analytics

Get a Diverge persona's full profile as JSON, including every enabled section's content. Omit persona_slug to use the user's default persona. The response also lists the user's other personas so you can switch.

get_profile

List the user's Diverge personas (slug, name, and which is the default). Use a slug with the other tools to act on a specific persona.

list_personas

Make a change to a Diverge persona. Operations: 'update_persona' (fields={...} of persona-level fields like name/description/full_name/style_*); 'add_item' (section_id + data={...}); 'update_item' (section_id + data, plus item_id for multi-record sections); 'delete_item' (section_id, plus item_id for multi-record sections); 'set_section' (section_id + enabled/order to toggle or reorder a section). Single-record sections (basic_info, professional_summary, my_story) need no item_id — add_item and update_item both upsert the one record. Call describe_section for a section's field schema, and get_profile for existing item ids.

update_profile