Skip to main content
Glama

4dayweek.io Jobs

Search jobs

search_jobs
Read-onlyIdempotent

Search live job listings with genuinely better working hours.

Every listing carries an explicit schedule_type, so you never have to infer one:

  • "4_day_week": 36 hours or less, 100% salary. The ONLY type that is reduced hours at full pay.

  • "4_day_week_pro_rata": four days at pro-rata (reduced) pay.

  • "9_day_fortnight", "half_day_fridays", "rotating_4_day", "summer_fridays", "part_time": other genuinely reduced-hours patterns.

  • "compressed_week": a 4x10. The SAME 40 hours in four days. NOT a 4-day week, and never to be described as one.

  • "async_hours", "flexible_hours", "unlimited_pto", "generous_pto", "flex_fridays", "no_meeting_days", "generous_parental_leave", "best_place_to_work": a full working week with a flexibility or leave policy.

To answer "find me a 4-day week job", pass schedule_type="4_day_week". Passing nothing returns all reduced-hours AND flexibility listings, which is usually broader than the user meant.

On locations: a job with no location restriction is worldwide-remote, so it matches ANY country filter. A large result count for a country therefore does not mean those roles are based there. Read each result's "locations" and "work_arrangement" before saying a job is in a particular place.

Results can also be narrowed by seniority (level), by skill/technology slugs, by a minimum work-life score and by how recently the employer posted.

Paging: a response returns at most 25 jobs and carries page, page_size, returned, has_more and, when another page exists, next_page. total_matching is the size of the whole match set. With a query it counts full-text matches over title AND description, so a job can be counted for a word that appears only in its body.

Each result carries the job's url on 4dayweek.io and its slug; get_job takes that slug and returns the full listing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default 1, maximum 200.
levelNoSeniority. One of entry, mid, senior, lead, executive.
limitNoResults per page. Default 10, maximum 25.
queryNoFree-text search over job title and description.
skillsNoSkill, technology or tool SLUGS, lowercase and hyphenated, e.g. react, python, customer-support. A job matches if it carries ANY of them.
countryNoCountry name, e.g. United Kingdom or United States. Matches jobs with an office in that country AND remote jobs open to it — including worldwide-remote roles, which match every country. Check each result's locations field before describing a job as being IN that country.
categoryNoJob category, e.g. engineering, product, design, marketing, sales, data, devops, finance, hr, legal, operations, security, content, customer-success.
schedule_typeNoFilter by schedule type. Use 4_day_week for a genuine 4-day week at full pay. compressed_week is a 4x10 and is NOT a 4-day week.
work_arrangementNoOne of remote, hybrid or onsite.
posted_after_daysNoKeep only jobs the employer posted within this many days, 1 to 365.
min_work_life_scoreNoKeep only jobs whose work-life score is at least this, on a 0-100 scale. The site's own filter offers 55, 70 and 85. See /methodology for how it is calculated.

Output Schema

NameRequiredDescriptionDefault
jobsNo
noteNo
pageNo
has_moreNo
returnedNo
next_pageNo
page_sizeNo
paging_noteNo
total_matchingNo
paging_limit_reachedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the read-only/open-world annotations it discloses non-obvious behavior: worldwide-remote jobs match every country filter, so a high country count does not mean those roles are based there, and total_matching counts full-text hits over title AND description so a match can come only from body text. Paging limits (25 per response, next_page only when has_more) are spelled out even though an output schema exists.

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?

Purpose is front-loaded and the bulleted taxonomy is scannable, with the location and paging caveats placed after the filter guidance. It is longer than strictly necessary for a search tool, and the schedule_type enumeration overlaps with what the explain_schedule_type sibling presumably covers, but every section still contains decision-relevant content.

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?

For an 11-parameter, zero-required search tool with pagination, this covers the two failure modes an agent would otherwise hit: choosing the wrong schedule_type and mis-reading country matches. Return shape is correctly left to the output schema, with only the paging fields and per-result url/slug highlighted because they drive the next call.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description still adds meaning the schema cannot: the full schedule_type taxonomy with the critical 4_day_week vs compressed_week distinction, and the warning that 4_day_week is the only reduced-hours-at-full-pay type. It also explains the consequence of omitting schedule_type, which no schema description states.

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 opening sentence names a specific verb and resource ('Search live job listings') and adds a scoping qualifier ('genuinely better working hours') that distinguishes the corpus from a generic job board. It is clearly distinct from get_job, get_company and search_companies without needing their schemas.

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?

It states the exact invocation for the canonical user intent ('to answer "find me a 4-day week job", pass schedule_type="4_day_week"') and warns that passing nothing returns a broader set than the user likely meant. It also names the follow-up tool and the field to hand it ('get_job takes that slug'), so the agent knows the next step as well as the current one.

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.