Skip to main content
Glama

Search company jobs (Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee)

search_jobs
Read-onlyIdempotent

List open jobs from a company career page on Greenhouse, Lever, Ashby, Workable, SmartRecruiters or Recruitee. Use when asked what a company is hiring for. Returns title, department, location, remote flag, salary when published, posted date and apply URL. Max 10 rows per call, up to 5 companies. When company values are plain slugs (e.g. "airbnb"), ats is required; it is not needed for prefixed values such as ashby:ramp or a career-page URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
atsNoRequired when company values are plain slugs. Not needed for ashby:ramp or a career-page URL.
limitNoRows to return (default 10).
remoteNoOnly remote jobs.
companyYesCompany slugs or career-page URLs, e.g. "airbnb". Max 5.
excludeNoSkip jobs containing these words.
keywordNoOnly jobs whose title or text contains one of these.
locationNoLocation filter, e.g. "United States".
posted_within_daysNoOnly jobs posted in the last N days (0 = any).
include_descriptionNoInclude the full job description text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the result shape (title, department, location, remote flag, salary when published, posted date, apply URL) and two hard constraints: max 10 rows per call and up to 5 companies. It does not mention rate limits or what happens for an unsupported or unparseable career page, which is the remaining gap.

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

Conciseness4/5

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

Four sentences, front-loaded with the action, then usage trigger, then return shape, then the trickiest parameter rule. The ATS platform list is repeated from the title, which is a small redundancy, but nothing else is wasted.

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?

For a 9-parameter, multi-backend search with no output schema, the description covers purpose, result fields, and the row/company caps an agent needs to plan queries. Only edge-case behavior (invalid slugs, silent skips, empty results) is left undocumented.

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

Parameters4/5

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

Schema coverage is 100%, so the bar is baseline 3, but the description adds real semantics by explaining the interaction between company and ats — plain slugs require ats while prefixed values like ashby:ramp or a career-page URL do not. That conditional rule is the main source of invocation error and it is spelled out in prose.

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?

States a specific verb and resource ("List open jobs from a company career page") and enumerates the supported ATS backends, so an agent knows exactly what this retrieves. No sibling tool in the list touches jobs or hiring, so disambiguation is trivially satisfied.

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?

Gives an explicit trigger ("Use when asked what a company is hiring for") plus a conditional rule about when the ats parameter is needed versus when it can be omitted. It stops short of naming alternatives or stating when not to use the tool, which is acceptable given the unrelated sibling set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources