recruiter-roles-mcp
Server Details
Search Recruiter Roles: live recruiter jobs, companies, sectors, locations, and market stats.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
7 toolsget_companyGet company profileRead-onlyIdempotentInspect
Fetch a single company's full profile plus a paginated list of its active jobs.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page of the company's jobs. Default: 1. | |
| slug | Yes | The company slug (e.g. 'robert-half'). | |
| per_page | No | Jobs per page. Default: 20, max: 100. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes |
get_jobGet job detailRead-onlyIdempotentInspect
Fetch the full detail for a single job by its slug, including the complete description, requirements, benefits, tech stack, and apply contact.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The job slug (the last path segment of its URL, or the 'slug' field from search_jobs). |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes |
list_companiesList recruiting companiesRead-onlyIdempotentInspect
Browse the directory of recruiting companies and agencies with their active job counts. Filter by name, company type, or HQ country.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search company name. | |
| page | No | Page number. Default: 1. | |
| sort | No | Sort order. Default: job_count. | |
| country | No | HQ country code (e.g. 'US', 'GB'). | |
| per_page | No | Results per page. Default: 20, max: 100. | |
| company_type | No | Company type filter. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| meta | Yes | |
| response_generated_at | No |
list_locationsList locationsRead-onlyIdempotentInspect
List the location hierarchy (countries, regions, or cities) with active job counts. Use the returned codes/slugs for the 'state' and 'city' filters in search_jobs.
| Name | Required | Description | Default |
|---|---|---|---|
| level | No | Hierarchy level to return. Default: countries. | |
| region | No | Filter cities by region code (e.g. 'TX'). Use with level=cities. | |
| country | No | Filter by country code (e.g. 'US', 'GB'). |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| response_generated_at | No |
list_sectorsList sectorsRead-onlyIdempotentInspect
List all recruiting sectors with their current active job counts. Use the returned slugs for the 'sector' filter in search_jobs.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| response_generated_at | No |
market_statsRecruiter job market statsRead-onlyIdempotentInspect
Aggregate market overview: total active jobs, posting velocity (24h / 7d), and breakdowns by sector, employment type, work arrangement, and country.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| response_generated_at | No |
search_jobsSearch recruiter jobsRead-onlyIdempotentInspect
Search live recruiter and talent-acquisition job listings on Recruiter Roles. Supports full-text search and filtering by sector, location, employment type, work arrangement, salary, and recency. Returns a paginated list with salary, company, location, and a tracked apply URL.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Full-text search across job title and company name. | |
| city | No | City slug, comma-separated (e.g. 'dallas-tx'). | |
| page | No | Page number. Default: 1. | |
| sort | No | Sort order. Default: recent. | |
| state | No | State/region code, comma-separated (e.g. 'TX,NY,BC'). Use list_locations for codes. | |
| sector | No | Sector slug, comma-separated for multiple (e.g. 'technology,financial-services'). Use list_sectors for valid slugs. | |
| per_page | No | Results per page. Default: 20, max: 100. | |
| is_remote | No | Shorthand for work_arrangement=remote. | |
| salary_min | No | Minimum salary in USD. Only returns jobs with a disclosed salary at or above this. | |
| source_type | No | 'direct' = employer-posted, 'scraped' = aggregated. | |
| posted_since | No | ISO date — jobs posted on or after this date. | |
| updated_since | No | ISO datetime — for incremental sync; jobs updated on or after this. | |
| employment_type | No | Employment type filter. | |
| salary_disclosed | No | true = only jobs with a disclosed salary; false = only undisclosed. | |
| work_arrangement | No | Work arrangement filter. |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| meta | Yes | |
| response_generated_at | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!