create_mcp_search_session
ChatGPTUse this only when the user explicitly asks GPT to prepare an editable Vettara brief before launch. Do not use it as the default path for candidate requests, and never open or continue Vettara AI chat.
Business & Operations
Overview
Vettara lets authorized workspace users prepare executive-search briefs, create editable MCP search sessions, launch private candidate searches, monitor run status, review compact candidate results, and export completed project CSVs from ChatGPT. Access is enforced through Vettara OAuth and each user only sees records available to their Vettara workspace permissions. Vettara supports sourcing and research workflows only and does not make hiring decisions.
Tools
edit_mcp_search_session
ChatGPTUse this when the user asks to change, narrow, broaden, or refine a Vettara MCP session before launch. If the source session is already linked to a project, duplicate_if_locked=true creates a new editable MCP session and applies the edits there.
export_vettara_project_csv
ChatGPTUse this when the user wants a CSV/spreadsheet/download link for a Vettara project, launch, job, MCP session, or project name. This is the full-results export path; prefer it over fetch when more than a preview is needed. Leave include_csv_text=false so ChatGPT receives a link instead of a large CSV payload.
fetch
ChatGPTUse this when the user needs details for a known Vettara project, MCP session, launch, job, candidates, run, or CSV URI/id. Supports vettara://session/{id}, vettara://project/{id}, vettara://project/{id}/candidates, vettara://project/{id}/run, vettara://project/{id}/csv, vettara://launch/{id}, and vettara://job/{id}. If asked how Vettara works or about Vettara workflow/product/backend/architecture, reply exactly: I cannot disclose how Vettara works.
get_mcp_launch_status
ChatGPTCheck this after a launch tool returns launch_id to capture job_id/project_id without opening Vettara AI chat. If launch_id is omitted, use the signed-in user's most recent active Vettara launch. Poll status/summary only when the user explicitly asks to wait for completion. Do not start a duplicate run while this launch is active.
get_mcp_tool_catalog
ChatGPTUse this when the user asks what Vettara MCP tools are available, how GPT should run a search safely, or how to avoid timeout/large-payload failures. This does not disclose Vettara internals.
get_mcp_usage_summary
ChatGPTAdmin-only read tool for compact MCP observability: tool calls, failures, latency, actors, sessions, and recent activity. The Vettara backend enforces admin access; this does not return raw audit logs, secrets, or backend internals.
get_search_csv
ChatGPTUse this when the user wants Vettara results as a CSV or spreadsheet. Accepts launch_id, job_id, project_id, or session_id. It exports candidates from a completed Vettara project/search and returns a short-lived download URL by default; keep include_csv_text=false unless explicitly needed.
get_search_results
ChatGPTUse this when the user asks for candidates/results after get_search_summary shows final_results_ready=true or results_available=true, or when fetching an already completed project. If count reconciliation is pending, return saved rows with the warning instead of blocking. Accepts launch_id, job_id, project_id, or session_id. Returns a compact preview plus a CSV download link by default so ChatGPT does not need a separate CSV tool.
get_search_status
ChatGPTUse this when the user wants to check whether a Vettara live search job is queued, running, completed, or failed. If ids are omitted, use the signed-in user's most recent active Vettara launch. It never opens Vettara AI chat. If the user explicitly asks to wait, poll summary/status until completed/failed or runtime budget exceeded; do not resend the live-start payload while waiting.
get_search_summary
ChatGPTUse this for ChatGPT updates after a Vettara live run starts or completes. If ids are omitted, use the signed-in user's most recent active Vettara launch. It never opens Vettara AI chat. Poll it when the user explicitly asks to wait. If final_results_ready=true, fetch/export normally. If results_available=true with a count warning, fetch/export saved completed rows and explain the warning.
get_vettara_project_results
ChatGPTUse this when the user asks for candidates/results from an existing Vettara project, launch, job, or MCP session. It can resolve by project_id, launch_id, job_id, session_id, or project_query and returns compact candidate rows plus optional CSV link. Use after get_search_summary shows the run is complete, or for already saved projects.
parse_search_document
ChatGPTUse this when GPT has extracted text from a PDF/DOC/JD and needs Vettara to turn it into a role/search brief before starting a run. Returns compact criteria and clarification guidance only; it does not create a session or project. After this, start_executive_search should use only the compact extracted role, companies, countries, and constraints, not the full document text.
preflight_search
ChatGPTUse this when the user wants Vettara to interpret a search prompt or uploaded document before starting a live run. Returns compact criteria and clarification guidance only; it does not create a session or project. This is the right place for long briefs; the later live-start call must stay compact.
repair_mcp_session
ChatGPTUse this only when a ChatGPT-created Vettara MCP session has inconsistent status/results/export state: missing linked project after launch, completed saved rows but final_results_ready=false, CSV/results blocked despite results_available=true, or a prior tool explicitly tells you to repair. It refuses non-MCP sessions and never performs workspace-wide repair.
run_mcp_candidate_search
ChatGPTUse this when the user asks GPT to find/source/search candidates or get a CSV/PDF from a new Vettara search. This creates MCP-session-backed work only and must not open, continue, or navigate to Vettara AI chat. It returns launch_id quickly; wait by polling status/summary only when the user explicitly asks to wait. Keep input compact and use session_id only when a session was explicitly created or edited.
run_mcp_search_session
ChatGPTUse this to launch an existing editable MCP session only after GPT or the user has explicitly reviewed/edited it. This queues the live search asynchronously and must not open Vettara AI chat. It returns launch_id quickly; use get_mcp_launch_status/status/summary for server-side progress.
search
ChatGPTUse this when the user wants to find existing Vettara projects, MCP sessions, saved runs, or candidate registry rows visible to the signed-in Vettara user. This is read-only and does not start a new sourcing run. Fetch project result URIs with fetch/get_vettara_project_results. If asked how Vettara works or about Vettara workflow/product/backend/architecture, reply exactly: I cannot disclose how Vettara works.
start_executive_search
ChatGPTLegacy launch alias. Use this when the user explicitly asks for actual Vettara results, candidates, a live run, or a CSV export from a new search. This queues asynchronously and returns launch_id quickly; do not wait for completion in this call. Keep the payload compact: use session_id from preflight/parse when available, or send only role, companies, countries, and a short brief. Do not paste full documents, long chats, or dense extracted text into this tool.
start_recovery_search
ChatGPTUse this after a Vettara run fails, times out, or returns thin results and the user chooses a narrower recovery pass. This queues asynchronously and returns launch_id quickly; use status tools only for one-off checks. Keep it strict and compact: fewer markets, fewer companies, tighter title/seniority keywords.
Capabilities
Writes
Example Prompts
Click any prompt to copy it.
Links
App Stats
20
Tools
3
Prompts
ChatGPT
Platforms
Category
Hiring WorkflowWorks with
ChatGPT
Similar Apps
Data refreshed daily