Gojiberry

Preview the upcoming actions of a LinkedIn or multi-channel campaign (one with a LinkedIn seat), as shown in the Scheduled tab of the app. For email-only campaigns use `get_campaign_email_queue` instead — this tool fails on them. Returns one entry per scheduled contact: the `contact`, the `campaign`, the `campaignStep` to run next (invitation, invitationNote, message, voiceMessage, visitProfile, likePosts or email) with its message filled with the contact variables, and `lastContactStep`, the last step the contact already received (absent for a contact entering the campaign). The queue is capped at the LinkedIn seat's full daily quotas (shared between the campaigns on that seat; today's actions are not subtracted) and at the remaining daily quota of the email seats. Preview only: nothing is sent, no new contacts are pulled in, no AI messages are generated and no credits are used. An inactive campaign has an empty queue. Useful for questions like 'what will this campaign send next' or 'who is about to be contacted'.

get_campaign_queue

Get detailed information about a single contact by ID.

get_contact

Legacy endpoint: get the LinkedIn (and email) conversations the user has had with a specific contact. Returns chats with their messages, ordered by most recent message first. The same data is available with pagination through `list_unibox_threads` and `get_unibox_thread_messages`.

get_unibox_for_contact

Free. Returns the suggested values for the `industry` filter of `search_leads` and `search_companies`, both as a flat list and grouped by category. Other industry values are accepted by the search tools, but these labels line up with the directory taxonomy and give the best results.

get_directory_industries

Get contact counts grouped by intent type. Useful for understanding the distribution of contact intents.

get_intent_type_counts

Get a single list by ID, including its contacts and its `campaignId` — the campaign agent that reaches out to them. Use this to resolve a source agent's `listId` into the campaign behind it: an empty `campaignId` (null or absent) means the list is linked to no campaign, so its contacts receive no outreach.

get_list

Get the organization of the authenticated user (company name, website, industry, size, owner ID, etc.).

get_organization

Get one source agent's full configuration, including the ICP (target job titles, industries, company sizes, locations, company types, ignored companies, mandatory keywords), its signals (`variables` — call this before editing them with `update_agent`, which replaces the whole list) and the `listId` of the list it imports sourced leads into. Source agents find leads; outreach is done by the campaign agent that uses the same list (see `get_campaign`) — source agent + list + campaign agent is a Full Cycle agent. To know which campaign outreaches this agent's leads, look its `listId` up by ID with `get_list` and read the list's `campaignId`. An empty `campaignId` (null or absent) means the list is linked to no campaign, so the leads this agent sources are never contacted: tell the user and offer to add the campaign with `create_campaign`.

get_agent

Get up to 100 recent run logs for a source agent, newest first. Useful for questions about how many leads an agent created, which signals produce leads, or whether recent signal runs failed.

get_agent_logs

Get paginated unibox messages for a thread owned by the authenticated user.

get_unibox_thread_messages

Act on behalf of another member of the organization. Once set, all subsequent tool calls in this session (contacts, campaigns, lists, agents, unibox, ...) are executed as that user, until impersonation is changed or cleared. Only works when the current API key belongs to the ORGANIZATION OWNER, and the target user must be a member of the same organization (member IDs are returned by `list_organization_members`). Passing `userId: null` stops impersonating and restores the key owner. This stores the impersonation on the current MCP session. For clients that open a new MCP session per tool call, the stateless `actAsUserId` argument available on every tool provides the same behavior on a per-call basis.

impersonate_user

Retrieve campaigns. A campaign is the campaign agent — what the Gojiberry platform calls an 'Agent': it performs the outreach (LinkedIn invitations, messages, emails, ...) to the contacts of its lists. Lead sourcing is done separately by source agents (see `list_agents`). By default (when `status` is omitted) this returns ALL campaigns — active AND inactive. Do not pass `status` unless the user explicitly asked for only active or only paused campaigns. `status` values: - "all" (same as omitting the argument): every campaign, regardless of state. - "active": ONLY campaigns currently running. - "inactive": ONLY paused campaigns — NOT all campaigns. If the user has no paused campaigns this returns an empty array even though active campaigns exist. Campaign membership in Gojiberry is driven by list membership, but the link is stored on the LIST, not on the campaign: the campaign objects returned here carry no list reference. To find which lists feed a campaign, call `list_lists` and keep the lists whose `campaignId` matches the campaign's `id`. Engagement metrics (reply rate, answered count, etc.) are derived from the contacts in the campaign's list: each contact carries a `campaignStatus` array of per-step records, each with a `type` (e.g. `message`, `voiceMessage`, `email`, `connection`, `view`, ...) and a `state` (e.g. `sent`, `delivered`, `answered`, `skipped`, ...). A contact counts as a reply when at least one `campaignStatus` entry has a `type` of `message`, `voiceMessage`, or `email` AND a `state` of `answered`; the reply rate is the number of contacts with a reply divided by the total contacts in the list.

list_campaigns

Retrieve contacts with optional pagination, search, and filtering. Returns a paginated list of contacts.

list_contacts

List the email seats (connected Gmail / Outlook mailboxes) of the authenticated user. Each seat has an `id` (usable in the `emailSeatIds` field of `create_campaign`), the mailbox `email`, sender `name` / `firstName` / `lastName`, `type` ('google' or 'outlook'), sending limits (`dailyEmailMax`, `dailyEmailCount`, `launchHour`, `activeDays`), tracking options (`trackOpening`, `removeUnsubscribeLink`), and warm-up status (`warmupEnabled`, `warmupCompleted`, `warmupStartedAt`). Call this before `create_campaign` when the campaign has `email` steps, to pick the seat(s) that will send them. When impersonating, the seats of the impersonated user are returned.

list_email_seats

Get paginated unibox (unified inbox) threads. Provide `seatId` to fetch threads for a specific LinkedIn seat; omit it to fetch threads across all seats in the account.

list_unibox_threads

Retrieve all lists with their contact counts. Each list carries a `campaignId`: the campaign agent that reaches out to its contacts, and the only place that link is stored. When `campaignId` is empty (null or absent), the list is linked to no campaign and its contacts get no outreach — if a source agent imports leads into it (see `list_agents`), those leads are sourced but never contacted, and the Full Cycle setup (list + source agent + campaign agent) is incomplete.

list_lists

List all members of the authenticated user's organization, with their user ID, name, email, role, and active status. When the API key belongs to the organization owner, a member's `id` is a valid target for impersonation (`impersonate_user` or the `actAsUserId` argument).

list_organization_members

List all source agents. A source agent is a lead finder: it continuously sources prospects matching the user's ICP and scores them with AI, importing them into its list. It does NOT do outreach — outreach (LinkedIn + email) is done by the campaign agent (see `list_campaigns`). Every source agent is linked to exactly one list (`listId`), and that same list is what a campaign agent reaches out to: list + source agent + campaign agent together form a Full Cycle agent. A source agent whose list is not used by any campaign is a 'legacy agent': it only sources leads, with no outreach. To find out which campaign (if any) outreaches an agent's leads, take the agent's `listId` and look that list up by ID with `get_list`: the list's `campaignId` is the campaign doing the outreach. When that `campaignId` is empty (null or absent), the list is linked to no campaign and the agent's leads are never contacted — offer to complete the setup with `create_campaign`. To check every agent at once, `list_lists` returns the `campaignId` of all lists in one call.

list_agents

Deactivate (pause) a campaign: it leaves the daily outreach scheduling and stops sending new steps. Messages and invitations already sent are NOT retracted, and the campaign, its lists and the contacts' progress are all kept — reactivate it with `activate_campaign` to resume where it left off. This is the safe way to stop a campaign; use it instead of deleting when the user asks to stop, pause, or halt outreach. Returns the resulting campaign state, so `active` on the response confirms the change. Calling this on an already-paused campaign is a no-op. Rate limited to 10 status changes per minute across `activate_campaign` and `pause_campaign`, so pause campaigns one at a time and expect a rate-limit error when stopping more than 10 at once.

pause_campaign

Reject a lead: the contact disappears from the review queue, is excluded from campaign scheduling (`readyForCampaign` is reset to false), and will not be picked up by automatic campaign launches. The rejection records who rejected the lead and when (`rejectedAt` / `rejectedByUserId` on the returned contact). Providing a `reason` is optional but recommended: reasons are stored on the contact and help understand why leads are rejected so targeting can be refined. Use one of the stable reason codes when the lead does not match the targeting; use 'other' together with `reasonText` for anything else (`reasonText` is required with 'other' and ignored for the other codes). Calling this on an already-rejected contact only updates the reason (latest reason wins); the original rejection timestamp and reviewer are kept. A rejection is reversible with `unreject_contact`.

reject_contact

Remove contacts from a list. Because campaign membership is driven by list membership, this also removes the contacts from any campaign linked to the list. The contacts themselves are not deleted.

remove_contacts_from_list

Reveal full company objects from the directory (name, description, website, LinkedIn URL, funding data, exact headcount, ...). This is intended for detailed company research beyond the company information included when revealing a lead. Never call it as a follow-up to `reveal_leads` just to get the leads' companies; that would use the user's credits a second time for data they already have. Revealed companies are returned in the tool response only. They are NOT imported or saved into the Gojiberry account. Credit usage: 0.5 credit from the user's Gojiberry plan per company actually returned (ids that resolve to no document use nothing). Revealing the same id twice uses credits twice, so avoid re-revealing ids you already have. If the remaining credits cannot cover all requested ids, only the first ids that fit are revealed. User confirmation required: never call this tool on your own initiative. Before calling, tell the user how many companies would be revealed and how many credits that uses, and wait for them to confirm. A generic request like 'find me companies' is not a confirmation — only reveal once the user has approved the credit usage. `ids` come from `search_companies` (the `id` field — the numeric LinkedIn organisation id). Max 100 ids per request; duplicates are de-duplicated.

reveal_companies

Reveal full lead objects from the directory (name, company, LinkedIn profile URL, website, country, ...). Emails/phones are NOT included — enrichment is a separate feature. COSTS CREDITS: 0.5 credit per lead actually returned (ids that resolve to no document are not charged). Revealing the same id twice charges twice, so avoid re-revealing ids you already have. If the balance cannot cover all requested ids, only the first affordable ids are revealed and charged. REQUIRES EXPLICIT USER CONSENT: never call this tool on your own initiative. Before calling, tell the user how many leads would be revealed and the credit cost, and wait for their explicit confirmation. A generic request like 'find me leads' is NOT consent to spend credits — only reveal after the user has approved the spend. Pass `listId` (one of your lists, see `list_lists`) to also save the revealed leads as contacts into that list at no extra credit cost — leads already in the workspace, excluded, or missing a first/last name are skipped. The save is synchronous, so a large reveal with `listId` can take noticeably longer. `ids` come from `search_leads` (the `id` field — the LinkedIn member id). Max 100 ids per request; duplicates are de-duplicated.

reveal_leads

Search the Gojiberry companies directory (shared pool). Free — uses no credits. Returns MASKED company previews: only `id`, `size`, `industry`, and `headquarters` are filled; every other field (name, website, description, ...) is returned empty. Use `reveal_companies` with the returned `id`s to get the full objects (0.5 credit each). Use this company directory only when the user explicitly wants detailed company data (description, funding, exact headcount, ...). It is NOT needed to get a lead's company: `reveal_leads` already includes it with no extra credits. Companies searched or revealed here are not imported into the Gojiberry account. At least one filter is required. Results are deterministic (same filters + page always return the same companies). `technologiesUsed` disclaimer: a company 'uses' a technology when that technology was mentioned in at least one of the company's job offers in the past months. It signals the company hires for that technology, NOT a verified install base.

search_companies

Search the Gojiberry leads directory (shared pool) to buy leads matching your criteria. FREE — no credits are consumed. Returns MASKED lead previews: only `id`, `firstName`, `jobTitle`, `location`, and `industry` are filled; every other field (lastName, company, profileUrl, ...) is returned empty so you can see which columns become available after revealing. Use `reveal_leads` with the returned `id`s to get the full objects (0.5 credit each). At least one filter is required (no filters returns an empty result). Results are deterministic: the same filters + page always return the same leads. Deep paging is capped at 10,000 results. For the `industry` filter, prefer the values returned by `get_directory_industries` (it's a soft preference/boost, not a hard filter).

search_leads

Send a social message to a real person in an existing unibox thread (delivered through the thread's social conversation). This delivers an actual message to the thread's attendee and cannot be undone. `chatId` is the internal thread ID returned as `id` by `list_unibox_threads`, not the social conversation URN.

send_unibox_message

Reverse a rejection: clears `rejectedAt`, `rejectedByUserId` and the stored reason, putting the contact back in the review queue. This does NOT approve the lead — `readyForCampaign` is reset to false, so the contact still needs to be accepted (e.g. with `update_contact` setting `readyForCampaign` to true) before it is picked up by a campaign. Because `readyForCampaign` is always reset, calling this on an approved contact moves it back to the review queue.

unreject_contact

Update a campaign's name, associated list IDs, and/or the MESSAGES of its steps. This tool CANNOT start or stop a campaign — use `activate_campaign` and `pause_campaign` for that. IMPORTANT — this tool edits the messages inside existing steps, NOT the steps themselves: - Steps CANNOT be added, removed, or reordered. If `steps` is provided, it must contain exactly the same number of steps, in the same order, with the same `type` values as the existing campaign (the API rejects the update otherwise). The current steps array is returned by `get_campaign`; only the message fields of that array should be edited. - Only the message content (`message`, `subject`, `note`) and `messageMode` of each step are applied; other step settings (delays, attachments, etc.) are left unchanged. `messageMode` (for `message` and `email` steps only): - `same` — every contact receives the same content; the message body is required (`message`, plus `subject` for email steps). - `ai` — no message content needed; Gojiberry generates a contextual, personalized message per contact.

update_campaign

Update an existing contact's fields. Only provided fields will be changed.

update_contact

Update a source agent's configuration, including its ICP (job titles, industries, company sizes, locations, etc.) — the ICP lives on the source agent.

update_agent