Skip to main content
Glama

recruiter-roles-mcp

by io.github.pcmarts

Search recruiter jobs

search_jobs
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFull-text search across job title and company name.
cityNoCity slug, comma-separated (e.g. 'dallas-tx').
pageNoPage number. Default: 1.
sortNoSort order. Default: recent.
stateNoState/region code, comma-separated (e.g. 'TX,NY,BC'). Use list_locations for codes.
sectorNoSector slug, comma-separated for multiple (e.g. 'technology,financial-services'). Use list_sectors for valid slugs.
per_pageNoResults per page. Default: 20, max: 100.
is_remoteNoShorthand for work_arrangement=remote.
salary_minNoMinimum salary in USD. Only returns jobs with a disclosed salary at or above this.
source_typeNo'direct' = employer-posted, 'scraped' = aggregated.
posted_sinceNoISO date — jobs posted on or after this date.
updated_sinceNoISO datetime — for incremental sync; jobs updated on or after this.
employment_typeNoEmployment type filter.
salary_disclosedNotrue = only jobs with a disclosed salary; false = only undisclosed.
work_arrangementNoWork arrangement filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes
response_generated_atNo

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds behavioral context beyond the annotations by mentioning pagination, return fields (salary, company, location, tracked apply URL), and the live nature of listings. Annotations already convey read-only/idempotent safety, so the description supplements with useful operational details without being overly verbose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences that front-load the purpose, list key capabilities, and state the output format. Every sentence adds value with no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 15 parameters and a rich schema, the description provides a sufficient high-level overview without needing to enumerate every filter. It covers the return format and scope, though it doesn't explicitly guide usage of list_locations/list_sectors for valid values (that's in schema descriptions). Overall, it's complete enough for effective tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all parameters are already documented. The description provides a high-level summary of filtering capabilities but doesn't add new meaning beyond the schema's per-parameter descriptions. It mentions 'recency' but doesn't map it to posted_since/updated_since explicitly, leaving some ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Search') and resource ('live recruiter and talent-acquisition job listings on Recruiter Roles'). It distinguishes itself from sibling tools by focusing on job search, while siblings handle companies, locations, sectors, or individual jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context that this tool is for searching job listings and lists the supported filters, implying when it should be used. It doesn't explicitly mention alternatives or exclusions, but the purpose is unambiguous enough for an agent to determine applicability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All recruiter-roles-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct resource or action: companies, jobs, locations, sectors, market stats, and search. There is no overlap in purpose, and the descriptions clarify what each tool returns.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (get_company, list_companies, search_jobs). market_stats is a noun phrase, which deviates slightly, but the overall naming style is consistent and predictable.

Tool Count5/5

Seven tools is well-scoped for a recruiter job board. Each tool serves a clear function, and the count is neither too thin nor excessive.

Completeness5/5

The domain is browsing and searching recruiter job listings. The surface covers listing, searching, fetching details, and market overview, with no obvious gaps for a read-only job board.

Resources