check_email_draft
ChatGPTUse this when an email draft has been written or revised with a winery marketer, or when they share a draft and want to know how it compares with what wineries typically send for the same kind of email, and with the user's own winery's past emails: subject length and specificity, urgency and whether it's backed by a real date or quantity, club mentions, storytelling, offer size and length. It reads the copy only, not the design or images. Each facet comes back as typical, less common or distinctive, with the share of comparable emails. When the user's winery has saved details, it also checks the draft's facts against them (vintages, amounts, saved limits on offers, event dates, codes, club statements, words to avoid): each claim is supported, conflicting or unverified, with the saved section and its date. It is not a grade or a prediction: distinctive can be good. Use the result to revise the draft together. The draft isn't stored.
compare_periods
ChatGPTUse this when a winery marketer or agency asks what changed in what wineries send between two periods, e.g. "what changed among my peers since last harvest?" or "how is this holiday season different from last year's?". It compares the same wineries in both periods (only those that sent in both), by default the user's peers over the last 90 days against the same 90 days a year earlier: how often they send, the mix of email types, and the share with an offer, urgency, a story or a club mention, with the change in percentage points and each period's email and winery counts. Give state, area or type to compare a wider set instead. It reports changes in what was sent, never what worked.
get_email_archetypes
ChatGPTUse this when a winery marketer wants the common kinds of email wineries send, as archetypes found by grouping the archive on what each email contains (type, occasion, structure, offers, urgency, hero image): for example to pick a format for their next email or see which formats are rare. Each archetype comes with its share of the archive, its defining traits (and how much more common they are than average), when it's sent, and a link. Give a type to see the archetypes that kind of email falls into, with the share of that type in each. Archetypes describe what's common, not what works.
get_email_benchmarks
ChatGPTUse this when a winery marketer asks what's typical in winery email: the mix of email types, when wineries send (months, weekdays, hours), how they use urgency, which offer types are common, subject-line patterns, email structure and calls to action, imagery (what photos show and how they're shot: subject, framing, composition, lighting, people), or how they talk about their wine club, including when planning or drafting an email. Results describe what is typical in Joy Cork's archive of winery marketing email, with the sample size; they are not performance data (no open or click rates).
get_mailing_calendar
ChatGPTUse this when a winery marketer is planning upcoming emails and wants to see the wine year as wineries mail it: how many emails go out each month, which types dominate, and which occasions (holidays, harvest, releases) wineries build around, optionally for one state, one wine region (e.g. Napa Valley) or one email type. Good for building a 90-day plan.
get_my_winery
ChatGPTUse this when starting any planning or writing for the user's own winery, before drafting: it returns what they've told Joy Cork about their winery (voice, story, wines, club, calendar, rules, audiences, notes) and what Joy Cork has observed in the winery's own emails (how often it sends, its email types and usual offers, recent subjects, the wines it mentions with the amounts quoted, upcoming events, its email platform). Saved facts are the source of truth; observed patterns show how it usually writes. Sections still empty are listed so you can ask about them.
get_peer_briefing
ChatGPTUse this when a winery marketer asks what their peers or competitors have been sending lately ("what did my peers send this week?", "anything I should know before I plan?"): the emails the account's peer wineries sent in the last days (subject, type, occasion, offers, with links), how that compares with their usual volume, events and new wines they announced, and usually-active peers that went quiet. Peers are the account's peer sets, else wineries like its own. It describes what was sent, not how it performed.
get_profile
ChatGPTUse this when you need to know which Joy Cork account this connection is linked to: the person and their winery or agency account.
get_winery_profile
ChatGPTUse this when a winery marketer asks how a specific winery emails its customers: how often it sends, its mix of email types, its usual offers and urgency, its recent subject lines, and which email service it sends with (and when it changed services or sending domains), compared with all wineries Joy Cork follows. Use the winery's name; without one, the user's own winery. If Joy Cork doesn't follow that winery, say so; don't guess.
list_my_emails
ChatGPTUse this when the user shares their own email results (a CSV or table from Klaviyo, Mailchimp, Commerce7, WineDirect or similar: opens, clicks, revenue per send) or asks what their own emails had in common. Returns every email Joy Cork has collected from the user's own winery, one row per campaign, oldest first: when it was sent, the subject and what Joy Cork observed in it (type, occasion, audience, offers and codes, urgency, how it opens, its sections, subject-line traits, length, images, the hero image). Match each row to the user's report by subject and send date, then compare results across those traits. Paged: call again with the next page until has_more is false.
request_winery_coverage
ChatGPTUse this when the user wants Joy Cork to start following a winery it doesn't follow yet, for example a peer or competitor, and agrees to request it. Needs the winery's name and website. Joy Cork signs up for its emails; the request counts against the user's plan only once the first email arrives, and the user is emailed when it's done. If Joy Cork already follows it, it says so and nothing is counted.
save_winery_context
ChatGPTUse this when the user tells you facts about their own winery worth keeping for future emails (voice, story, wines with vintages, notes and amounts, club details, upcoming dates, shipping and offer rules, audiences, other notes) and agrees to save them. Write the section as clear plain text in your own words, only what the user said or confirmed. mode "append" adds to the section; "replace" rewrites the whole section, so use it only with the section's current text in hand. Saved details are visible to everyone on the user's Joy Cork account.
search_winery_emails
ChatGPTUse this when a winery marketer wants real examples of what other wineries sent: e.g. holiday gift emails, harvest event invitations, club shipment notes, new-release announcements. Returns short facts about each email (winery, date, subject, type, offers) with a link to view it in Joy Cork; it never returns the full email. Filter by type, occasion, state, month, dates sent, urgency tactic or offer type; add a query for words in the email. Narrow to examples a marketer can realistically adapt: with or without an offer, a word range, what the email opens with, a section it includes, or what its hero image shows (e.g. release emails with no offer, under 200 words, opening with a story). For recent activity ("this week", "lately") use sent_after with today's date in mind, newest first. Don't use it for consumer wine shopping or recommendations.
