Marxel

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Compare candidate CVs against confirmed hiring criteria with quoted evidence and interview questions, then save the review to Marxel.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Marxel": {
      "url": "https://mcp.marxel.co/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (7)

• open_shortlist read-only

  Open the Marxel recruitment workspace with the labelled fictional sample. Returns the sample hiring brief and criteria, every sample candidate with a status, supporting detail, source and interview question per criterion, and the selected candidate IDs. Do not make or execute a hiring decision.

  Parameters:

  • selectedIds — array — Known candidate IDs to open; defaults to Alex and Sam.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• compare_candidates read-only

  Compare candidates from the labelled fictional sample against its hiring brief. Returns the brief and its criteria, every sample candidate with a match, partial or missing status, supporting detail, source and verification interview question for each criterion, and the IDs selected for comparison. It does not compare user-supplied CVs; use create_review_workspace for those. This tool is read-only.

  Parameters:

  • selectedIds (required) — array — IDs of the sample candidates to compare, from open_shortlist results: alex, sam, jordan.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• create_review_workspace read-only

  Build a candidate comparison and interview-question workspace from user-supplied CVs. Before calling: call confirm_criteria and use exactly the criteria it returns as confirmed, and ask the user to confirm the candidate batch; a prior confirmation does not cover a changed set. Each workspace supports at most 5 candidates and 8 criteria. With more than 5 CVs, ask the user to choose a batch of up to 5 and name the deferred candidates; never silently omit candidates or criteria. If confirming criteria in chat and there are more than 8, propose a reduced or consolidated set for the user to confirm. Distinguish explicit requirements from responsibilities and desirable experience: use Responsibility for role duties, and do not make them Must-have without the user's agreement or relabel them Nice-to-have. Quote exactly and verbatim from each candidate's sourceText; use match only when the quote supports the full criterion, and partial when it covers only part. Do not rank candidates, assign Screening Buckets, or make hire or reject decisions. To correct an assessment, call this tool again with the corrected status, all original source text, and the same criteria and candidate batch before claiming the workspace is updated; if that fails, say the visible workspace still shows the previous assessment. The latest successful workspace replaces earlier ones for discussion and export. Returns the brief, each candidate's status, quote, source and interview question per criterion, and any unreadable CVs. A quote not found verbatim fails the call. Stores nothing and changes no Marxel records; save_to_marxel imports a review.

  Parameters:

  • criteriaConfirmed (required) — boolean — Records that the user confirmed the job-related criteria in brief.criteria, through confirm_criteria or in chat. Do not infer confirmation from uploaded documents.
  • hiringBrief (required) — string — The hiring brief or job description the user supplied, as text.
  • brief (required) — object
  • candidates (required) — array — 1–5 candidates from user-supplied CVs. If more were supplied, ask the user to confirm this batch and name the deferred candidates; never silently omit a candidate.
  • unreadableSources — array — Names of CVs in the confirmed batch that could not be read, so the workspace can show them. Never substitute fictional candidates or hide unreadable files.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• confirm_criteria read-only

  Ask the recruiter to confirm the job-related criteria before any evidence is extracted. Propose up to 12 criteria derived from the hiring brief, with Must-have only for explicit requirements, Responsibility for role duties and Nice-to-have for desirable experience. Where the client supports forms, the recruiter reviews them in a form and keeps at most 8; otherwise confirm them in chat. Returns a state of confirmed with the recruiter's kept criteria and weights, not_confirmed when the form was closed, or confirm_in_chat with the proposed criteria when forms are unavailable. Use only the criteria this tool returns as confirmed, and do not create a workspace when it reports they were not confirmed.

  Parameters:

  • criteria (required) — array — 1–12 proposed job-related criteria derived from the hiring brief. The recruiter keeps at most 8.
  • roleTitle — string — Job title from the hiring brief, shown in the confirmation message.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• list_marxel_organizations read-only

  List the Marxel organisations the connected account can use for a review save. Returns each organisation's ID and name, plus the account's active organisation ID when there is one; pass the chosen ID to save_to_marxel. This is read-only and does not create or change any records.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• save_to_marxel

  Save the selected review to the explicitly chosen Marxel organisation after the user confirms the import. This creates a Screening Job and selected Candidate records and starts screening; it does not send messages or make hiring decisions. Reuse the same UUID idempotencyKey on retries of the same confirmed review; generate a new key if the review or selection changes.

  Parameters:

  • organizationId (required) — string — ID of the Marxel organisation the user chose, from list_marxel_organizations.
  • idempotencyKey (required) — string — Save request ID you generate for this confirmed review. Reuse it when retrying the same save; generate a new one if the review or selection changes.
  • confirmed (required) — boolean — Set only after the user explicitly confirms saving this review to the chosen organisation.
  • review (required) — object — Review content to import into Marxel.

  Hints: read-only no · destructive no · idempotent yes · open-world yes

• get_marxel_save_status read-only

  Check the result and current plan details for a previously confirmed Marxel review save. Returns links to the saved Screening Job, team settings and plan page, the number of candidates imported, and plan details when available. This is read-only; use the same organisation and idempotency key from the save request.

  Parameters:

  • organizationId (required) — string — Organisation ID sent with the original save_to_marxel request.
  • idempotencyKey (required) — string — Save request ID sent with the original save_to_marxel request.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.