> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jobin.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Jobin MCP capabilities and tool reference

> Explore every Jobin MCP tool for candidate search, contact management, messages, outreach sequences, recruiting pipelines, tasks, and agency analytics.

Jobin MCP (Model Context Protocol) connects your AI assistant to recruiting and CRM data in your Jobin.cloud workgroup.
This reference lists every tool, including alternative names for the same action, plus the available policy resources and prompt.

New to Jobin MCP? [Connect your assistant first](/jobin-mcp#connect-your-assistant).
You can ask for these workflows in plain language; tool names are provided for clients and developers.

## Permissions and approvals

Read access retrieves information your account can access in the active workgroup.
Actions that change records require write access (`jobin:mcp.write`) and your explicit approval for each call.
Switching an OAuth workgroup requires approval even with read access; dashboard-issued MCP tokens remain tied to their original workgroup.

Some clients display all tools even when a connection has read access only. Ask your assistant to check
`jobin_get_mcp_capabilities`: `authorizedToolsForCurrentSession` identifies the tools your current connection can execute.
Workspace permissions, feature availability, and credit requirements still apply.

## Connection and workgroups

Check your connection and select the workspace for your recruiting work.

| Tool | Capability |
| - | - |
| `jobin_get_current_user_context` | Check the signed-in user and active workgroup. |
| `jobin_get_mcp_capabilities` | Check available tools, current permissions, and approval requirements. |
| `jobin_list_accessible_workgroups` | List workgroups you belong to and find the right team workspace. |
| `jobin_switch_workgroup` | Switch the active OAuth workgroup with approval. Chats sharing that connection share its workgroup. |

## Contact search, profiles, and conversations

Start here to find candidates or leads already saved in Jobin. These tools use read access.

| Tool | Capability |
| - | - |
| `jobin_search_contacts` | Search saved contacts by identity, role title, location, tag, sequence, tenure, contact channel, or a Job pipeline stage, with pagination. |
| `jobin_get_contact` | Review one contact's profile and every current Job pipeline membership. Private email addresses and phone numbers remain hidden; the result indicates whether they are available. |
| `jobin_get_private_channels` | Retrieve a contact's private email addresses and phone number when explicitly requested. |
| `jobin_list_contact_events` | Review a contact's timeline, including conversations, pipeline moves, and sequence exits. |
| `jobin_list_workgroup_messages` | Read email, social, and SMS message history across accounts visible to you under existing inbox-sharing permissions. Filter received messages to review replies. |
| `jobin_list_contact_notes` | Read recruiter notes for a contact. |
| `jobin_list_contact_documents` | List document metadata for a contact, such as details of an attached CV. This does not download document contents. |
| `jobin_list_contact_tags` | Discover workspace contact tags and their IDs for contact filtering, with pagination. |

## External candidate sourcing

Use external People Search when you explicitly want to expand beyond saved contacts. It requires write access and an eligible workspace.

| Tool | Capability |
| - | - |
| `jobin_search_people` | Find new people using structured company, role, location, similarity, and grouped matching filters. Returned profiles are saved to Jobin Contacts and consume credits. |

The first call prepares a Jobin approval link without spending credits. Review the exact search and maximum charge on that page,
then the assistant can submit the approved request with its approval ID. Each additional page or rerun needs separate approval.
Matching filters do not perform semantic candidate screening: assess profile fit after results are returned and saved.

## Contact management and enrichment

These tools require write access and approval. Alternative names are listed individually so you can identify every tool your client exposes.

| Tool | Capability |
| - | - |
| `jobin_create_contact` | Create or deduplicate one contact in the active workgroup. |
| `jobin_import_contact` | Import one contact into the active workgroup using the same import workflow as Create Contact. |
| `jobin_import_contacts` | Import up to 50 vetted contacts in one request. |
| `jobin_update_contact` | Update supported fields on one contact. |
| `jobin_patch_contact` | Alternative name for Update Contact, using the same supported fields. |
| `jobin_add_tag` | Create or reuse a tag and apply it to one contact. |
| `jobin_remove_tag` | Remove a tag from one contact by its ID or value. |
| `jobin_create_note` | Create a recruiter note for a contact. |
| `jobin_upsert_contact_note` | Create a note or update an existing contact note. |
| `jobin_trigger_enrichment` | Request selective enrichment for career details, social URLs, email addresses, or phone numbers. |
| `jobin_request_contact_enrichment` | Alternative name for Trigger Contact Enrichment, with the same options and approval requirements. |
| `jobin_upload_contact_document` | Upload one base64-encoded contact document, such as a CV, up to 10 MB. |

Before enrichment, review and accept the credit cost for the requested data and workspace mode.
The final charge can be lower or zero when no new billable data is stored.
If enrichment is processing, the assistant can check the contact again for the result.

## Follow-ups and tasks

Review follow-ups with read access; creating a task requires write access and approval.

| Tool | Capability |
| - | - |
| `jobin_list_contact_tasks` | List a contact's open tasks by default, or request completed tasks. |
| `jobin_create_contact_task` | Create a contact task or call with details such as an assignee, date, time, priority, and reminder. |

## Outreach sequences and performance

A campaign in tool names is an outreach sequence in Jobin. List, detail, and report tools use read access.
Adding or removing contacts requires write access and approval; these actions work with existing sequences.

| Tool | Capability |
| - | - |
| `jobin_list_campaigns` | Find outreach sequences, including filtering by name. |
| `jobin_get_campaign` | Review one sequence and its stage metadata. |
| `jobin_get_sequence_report` | Review summary, funnel, channel, timeline, diagnostic, and step performance with optional dates and daily, weekly, or monthly buckets. |
| `jobin_add_to_campaign` | Add contacts to an existing outreach sequence. |
| `jobin_remove_from_campaign` | Exit contacts from an outreach sequence with an audit event. |
| `jobin_add_to_sequence` | Alternative name for Add to Campaign. |
| `jobin_remove_from_sequence` | Alternative name for Remove from Campaign. |

## Recruiting pipelines

Use the read tools to discover Jobs, stage IDs, and current memberships before a write. Pipeline
search filters apply to saved Contacts and compose with the existing contact filters. Stage and
sub-stage IDs are scoped to the selected Job; supplying both an ID and name requires a match.

| Tool | Capability |
| - | - |
| `jobin_list_jobs` | Find workgroup Jobs and discover their current stage trees, with bounded cursor pagination. |
| `jobin_get_job_pipeline` | Inspect one Job's ordered stages, sub-stages, and virtual Assigned/exit destinations by stable Job ID. |
| `jobin_assign_contact_pipeline_stage` | Assign one verified contact using discovered IDs or legacy exact names; requires write access and explicit approval. |
| `jobin_move_contact_pipeline_stage` | Move one verified contact from an expected current membership using discovered IDs or legacy exact names; requires write access and explicit approval. |

Example sequence: call `jobin_list_jobs`, inspect the chosen `jobId` with `jobin_get_job_pipeline`,
search with `jobin_search_contacts({ jobId, stageId })`, then inspect the chosen Contact with
`jobin_get_contact`. After explicit user approval, pass `contactId`, `jobId`, and `stageId` to
`jobin_assign_contact_pipeline_stage` or the source and destination selectors to
`jobin_move_contact_pipeline_stage`. Verify with `jobin_get_contact`; do not use a write attempt to
discover valid names. Legacy name-only calls remain supported. If an ID and name are both supplied,
the backend rejects them when they refer to different targets. A stale source membership must be
refreshed before moving.

## Agency analytics

These tools use read access and respect report visibility. Financial metrics require owner or admin access.

| Tool | Capability |
| - | - |
| `jobin_list_agency_analytics_metadata` | Discover the metrics and dimensions available to you in the active workgroup. |
| `jobin_run_agency_analytics_report` | Run a bounded report using supported metric and dimension IDs. |
| `jobin_load_agency_analytics_report` | Load and run a report you own or that is shared with your workgroup. |

## Background operations

| Tool | Capability |
| - | - |
| `jobin_list_operations` | Inspect background operations visible to you in the active workgroup, with pending work returned by default. Requires read access. |

## Outreach review prompt

Clients that support MCP prompts can use this read-only workflow with a contact ID and optional role context.

| Prompt | Capability |
| - | - |
| `jobin_review_contact_for_outreach` | Review profile fit, personalization angles, missing information, and useful follow-up questions without changing records or sending messages. |

## MCP policy resources

Clients that support MCP resources can read the policies governing the connection.

| Resource URI | Purpose |
| - | - |
| `jobin://policy/mcp-v1` | General authentication, workgroup boundaries, approvals, and supported operations. |
| `jobin://policy/mcp-v1/read-only` | Rules for read access, inbox visibility, and workgroup context changes. |
| `jobin://policy/mcp-v1/write` | Rules for write access and approved actions. Available with write access. |
| `jobin://policy/mcp-v1/beta-write` | Compatibility alias for the write policy for older clients; omitted from discovery. |

## Current boundaries

MCP supports preparing outreach ideas and managing sequence membership. It does not provide direct email sending,
document downloads, bulk exports, raw database documents, or secrets.

[Return to the Jobin MCP setup guide](/jobin-mcp) to connect or troubleshoot your assistant.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.