Skip to main content
Glama

Find your role first

Search jobs

search_jobs
Read-onlyIdempotent

Find open jobs checked within 24 hours. Up to 20 results, newest posted first.

    query matches whole words in the title or company (e.g. "product manager", "quant", "ml engineer").
    location takes a country ("United States", "UK", "India") or a city or state as written.
    exclude drops titles containing any of these words ("senior staff intern").
    remote=true keeps remote roles only. posted_within_hours keeps recent postings.
    Call count_jobs first (free) to size a search before spending credits.
    Use published_since for source dates and discovered_since for new discoveries excluding baselines.
    Follow next_offset to paginate. No JD text is returned.
    experience keeps roles whose posting asks for these years of experience: any of
    "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (read, names none), "unchecked" (not read, or no text).
    Read from each posting; include not_stated and unchecked unless you mean to drop those roles.
    family="product_adjacent" finds product, product marketing, growth, customer success,
    forward deployed and business operations titles in one search; query narrows within it.
    roles takes several titles at once (["Product Manager", "Software Engineer"]) and matches any;
    locations likewise (["United States", "London", "Remote"]).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page, 1 to 20.
queryNoWhole words matched in the title or company, e.g. "product manager" or "quant". Empty for any.
rolesNoSeveral titles at once, matching any, e.g. ["Product Manager", "Software Engineer"]. Up to 40.
familyNo"product_adjacent" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it.any
offsetNoSkip this many results; pass next_offset from the previous page.
remoteNoOnly remote roles.
sourceNoOnly roles from one source (gh is Greenhouse), or "any".any
excludeNoLeave out titles containing any of these words, e.g. "senior staff intern".
locationNoOne country ("United States", "UK", "India"), or a city or state as written. Empty for anywhere.
locationsNoSeveral places at once, matching any, e.g. ["United States", "London", "Remote"]. Up to 8.
experienceNoYears of experience the posting asks for; any of "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (we read the posting and it names none) and "unchecked" (not read yet, or no text to read: many big-company and Workday roles). Include both unless you mean to drop them.
published_sinceNoISO date or time: only roles the company dated on or after it. Empty for any.
discovered_sinceNoISO date or time: only roles we first found on or after it, excluding baseline imports. Empty for any.
posted_within_hoursNoOnly roles posted within this many hours; 0 for any time.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "any",
      -  "gh",
      -  "ashby",
      -  "lever",
      -  "workday",
      -  "amazon",
      -  "microsoft",
      -  "netflix",
      -  "apple",
      -  "google",
      -  "meta",
      -  "eightfold",
      -  "jibe",
      -  "phenom",
      -  "atlassian",
      -  "successfactors"
      -]New value: +[
      +  "any",
      +  "gh",
      +  "ashby",
      +  "lever",
      +  "workday",
      +  "amazon",
      +  "microsoft",
      +  "netflix",
      +  "apple",
      +  "google",
      +  "meta",
      +  "eightfold",
      +  "jibe",
      +  "phenom",
      +  "atlassian",
      +  "successfactors",
      +  "radancy"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "any",
      -  "gh",
      -  "ashby",
      -  "lever",
      -  "workday",
      -  "amazon",
      -  "microsoft",
      -  "netflix",
      -  "apple",
      -  "google",
      -  "meta",
      -  "eightfold",
      -  "jibe",
      -  "phenom",
      -  "atlassian"
      -]New value: +[
      +  "any",
      +  "gh",
      +  "ashby",
      +  "lever",
      +  "workday",
      +  "amazon",
      +  "microsoft",
      +  "netflix",
      +  "apple",
      +  "google",
      +  "meta",
      +  "eightfold",
      +  "jibe",
      +  "phenom",
      +  "atlassian",
      +  "successfactors"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "any",
      -  "gh",
      -  "ashby",
      -  "lever",
      -  "workday",
      -  "amazon",
      -  "microsoft",
      -  "netflix",
      -  "apple",
      -  "google",
      -  "meta",
      -  "eightfold",
      -  "jibe",
      -  "phenom"
      -]New value: +[
      +  "any",
      +  "gh",
      +  "ashby",
      +  "lever",
      +  "workday",
      +  "amazon",
      +  "microsoft",
      +  "netflix",
      +  "apple",
      +  "google",
      +  "meta",
      +  "eightfold",
      +  "jibe",
      +  "phenom",
      +  "atlassian"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "any",
      -  "gh",
      -  "ashby",
      -  "lever",
      -  "workday",
      -  "amazon",
      -  "microsoft",
      -  "netflix",
      -  "apple",
      -  "google",
      -  "meta",
      -  "eightfold"
      -]New value: +[
      +  "any",
      +  "gh",
      +  "ashby",
      +  "lever",
      +  "workday",
      +  "amazon",
      +  "microsoft",
      +  "netflix",
      +  "apple",
      +  "google",
      +  "meta",
      +  "eightfold",
      +  "jibe",
      +  "phenom"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "any",
      -  "gh",
      -  "ashby",
      -  "lever",
      -  "workday",
      -  "amazon",
      -  "microsoft",
      -  "netflix",
      -  "apple",
      -  "google",
      -  "meta"
      -]New value: +[
      +  "any",
      +  "gh",
      +  "ashby",
      +  "lever",
      +  "workday",
      +  "amazon",
      +  "microsoft",
      +  "netflix",
      +  "apple",
      +  "google",
      +  "meta",
      +  "eightfold"
      +]
  6. Changed2 schema fields changed
    • changedInput schema / properties / experience / description
      Previous value: -"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (about a third of postings don't say; include it unless you mean to drop them)."New value: +"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (we read the posting and it names none) and \"unchecked\" (not read yet, or no text to read: many big-company and Workday roles). Include both unless you mean to drop them."
    • changedInput schema / properties / experience / items / enum
      Previous value: -[
      -  "0-1",
      -  "1-3",
      -  "3-5",
      -  "5-8",
      -  "8+",
      -  "not_stated"
      -]New value: +[
      +  "0-1",
      +  "1-3",
      +  "3-5",
      +  "5-8",
      +  "8+",
      +  "not_stated",
      +  "unchecked"
      +]
  7. Changed14 schema fields changed
    • addedInput schema / properties / discovered_since / description
      Added value: +"ISO date or time: only roles we first found on or after it, excluding baseline imports. Empty for any."
    • addedInput schema / properties / exclude / description
      Added value: +"Leave out titles containing any of these words, e.g. \"senior staff intern\"."
    • addedInput schema / properties / experience / description
      Added value: +"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (about a third of postings don't say; include it unless you mean to drop them)."
    • addedInput schema / properties / family / description
      Added value: +"\"product_adjacent\" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it."
    • addedInput schema / properties / limit / description
      Added value: +"Results per page, 1 to 20."
    • addedInput schema / properties / location / description
      Added value: +"One country (\"United States\", \"UK\", \"India\"), or a city or state as written. Empty for anywhere."
    • addedInput schema / properties / locations / description
      Added value: +"Several places at once, matching any, e.g. [\"United States\", \"London\", \"Remote\"]. Up to 8."
    • addedInput schema / properties / offset / description
      Added value: +"Skip this many results; pass next_offset from the previous page."
    • addedInput schema / properties / posted_within_hours / description
      Added value: +"Only roles posted within this many hours; 0 for any time."
    • addedInput schema / properties / published_since / description
      Added value: +"ISO date or time: only roles the company dated on or after it. Empty for any."
    • addedInput schema / properties / query / description
      Added value: +"Whole words matched in the title or company, e.g. \"product manager\" or \"quant\". Empty for any."
    • addedInput schema / properties / remote / description
      Added value: +"Only remote roles."
    • addedInput schema / properties / roles / description
      Added value: +"Several titles at once, matching any, e.g. [\"Product Manager\", \"Software Engineer\"]. Up to 40."
    • addedInput schema / properties / source / description
      Added value: +"Only roles from one source (gh is Greenhouse), or \"any\"."
  8. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive safety. The description adds cost behavior ('spending credits'), result recency ('checked within 24 hours'), ordering, pagination, and output limitation ('No JD text is returned'), which are not in the annotations.

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?

The description is front-loaded with purpose and usage, then organized by parameter, which suits a 14-parameter search. It is somewhat long because many parameter sentences duplicate the already-complete schema, but the structure remains clear.

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

Completeness5/5

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

Output schema exists, so return values need not be explained; the description still notes the absence of JD text and pagination behavior. Together with annotations and 100% schema coverage, it gives an agent enough context to call the tool correctly.

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 the schema already documents all 14 parameters. The description mostly repeats those same parameter details (query matching, location formats, experience enums) rather than adding substantial new semantics beyond the schema.

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 first sentence states a specific verb and resource ('Find open jobs') with scope ('checked within 24 hours') plus result ordering. It explicitly names count_jobs as the sizing alternative, distinguishing it from that sibling and from retrieval tools like get_job.

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

Usage Guidelines5/5

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

Explicitly tells the agent to call count_jobs first before spending credits, when to use published_since vs discovered_since, and to follow next_offset for pagination. It also states no JD text is returned and advises including not_stated/unchecked unless intentionally dropping roles.

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.