Skip to main content

Gem

Search your Gem pipeline and answer recruiting questions with live analytics.

Tools

15 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

15 tools found.

  • Get application

    Tool name: get_application

    Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…

  • Get job

    Tool name: get_job

    Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.

  • Get metrics catalog

    Tool name: get_metrics_catalog

    List the metrics and dimensions this team can report on with query_metrics.

  • Get person

    Tool name: get_person

    Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…

  • Get project

    Tool name: get_project

    Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).

  • Get saved report

    Tool name: get_saved_report

    Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.

  • Get sequence

    Tool name: get_sequence

    Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…

  • Get sequence tokens

    Tool name: get_sequence_tokens

    List the merge tokens available for writing a sequence stage's subject or body on this team.

  • Query metrics

    Tool name: query_metrics

    Run a recruiting-analytics query and get back an aggregated {columns, rows} table.

  • Search

    Tool name: search

    Quick cross-type lookup of a Gem entity by name or keyword — people, projects, sequences, dashboards, or jobs.

  • Search applications

    Tool name: search_applications

    List the candidates in one job's pipeline.

  • Search jobs

    Tool name: search_jobs

    Find jobs by criteria — turn a job name or req id into the ext_id other tools take, or browse a team's jobs.

  • Search people

    Tool name: search_people

    Find candidates by attribute across CRM and ATS — title, company, skills, location, years of experience, pipeline stage, scorecards, and contact recency.

  • Search users

    Tool name: search_users

    Resolve a teammate to their ATS ID (used for analytics queries and filters that rely on it) and Gem ID (used for tagging in notes).

  • Whoami

    Tool name: whoami

    Return the Gem user this session is authenticated as: user_id, team, email, client id, and the team's ATS (e.g. 'Gem ATS', 'Greenhouse').

Compatibility

Connect Gem to the clients your teams already use

27 AI clients can connect to Gem through Runlayer. Pick one for its setup steps and controls.

Why Runlayer

Why connect Gem through Runlayer?

One approved path

Approve Gem once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions