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.Contact search, profiles, and conversations
Start here to find candidates or leads already saved in Jobin. These tools use read access.External candidate sourcing
Use external People Search when you explicitly want to expand beyond saved contacts. It requires write access and an eligible workspace.
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.
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.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.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.
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.