Skip to main content
Glama

Jobs Base

by io.jobsbase

search_jobs

Read-only

Search and filter builder job listings on jobsbase.io — a curated board exclusively for "builder" roles (cross-functional positions where one person owns engineering, product, and delivery end-to-end: founding engineers, solo builders, 0-to-1 roles). Every job here is already an AI-native builder role, so do NOT search for generic terms like "builder", "AI", "full-stack", or "engineer" — they are redundant and will hurt results. Just use filters (country, workplace, seniority, etc.) to narrow down. Use q only for specific technologies, companies, or domain keywords. All parameters are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional keyword for specific technologies, domains, or companies (e.g. "React", "fintech", "Stripe"). Do NOT use generic terms like "builder", "AI", "engineer", or "developer" — every job on this board already matches those. Omit to browse all jobs.
cityNoFilter by city. Comma-separated for multiple: London,Berlin
sortNoSort order: relevance (best match first), posted_at (newest first, default), salary (highest salary first)
typeNoFilter by job type. Comma-separated for multiple: full-time,contract. Values: full-time, part-time, contract, freelance, internship
limitYesResults per page (default 30, max 100)
stateNoFilter by state/province name. Comma-separated for multiple: California,Texas
cursorNoCursor for next page of results
regionNoFilter by geographic region. Comma-separated for multiple. Values: north_america, latin_america, europe, asia_pacific, middle_east_africa
companyNoFilter by exact company name
countryNoFilter by country code. Comma-separated for multiple: US,GB,CA
workplaceNoFilter by workplace. Comma-separated for multiple: remote,hybrid. Values: remote, hybrid, on-site
posted_withinNoFilter by posting date: past 24h, 3d, 7d, 14d, or 30d
salary_at_mostYesShow jobs that can pay at most this amount annually (normalized to annual equivalent)
education_levelNoFilter by minimum education level
salary_at_leastYesShow jobs that can pay at least this amount annually (normalized to annual equivalent)
seniority_levelNoFilter by seniority. Comma-separated for multiple: mid,senior. Values: internship, entry, mid, senior, lead, executive
visa_sponsorshipYesSet to true to only show jobs that offer visa sponsorship
experience_no_more_thanYesShow jobs requiring no more than this many years of experience

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[
+  "salary_at_least",
+  "salary_at_most",
+  "experience_no_more_than",
+  "visa_sponsorship",
+  "limit"
+]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses a non-obvious behavioral trait: generic terms like 'builder' or 'AI' are redundant and 'will hurt results.' This adds valuable context about how the search engine processes queries. However, it doesn't mention pagination or result ordering behavior, so it doesn't fully maximize transparency.

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 dense but well-organized: it front-loads the purpose, then delivers a critical usage warning, then explains filter usage. Every sentence serves a clear purpose, though it could be slightly trimmed without losing value.

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

Completeness3/5

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

For an 18-parameter search tool with no output schema, the description gives strong domain context but omits pagination behavior (cursor parameter) and does not explain result structure or defaults beyond what the schema already covers. The 'all parameters optional' contradiction further undermines completeness.

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

Parameters2/5

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

While schema coverage is 100%, the description makes a blanket claim that 'All parameters are optional,' directly contradicting the input schema's five required parameters. This false statement misleads agents about required inputs. The guidance about q is helpful but does not compensate for this significant inaccuracy.

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 opens with 'Search and filter builder job listings on jobsbase.io' — a specific verb, resource, and scope. It clearly distinguishes this tool from siblings (get_job, list_filters) by emphasizing the search/filter capability and the unique 'builder roles' niche.

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?

Provides explicit when-to-use guidance: 'do NOT search for generic terms' and 'Use q only for specific technologies, companies, or domain keywords.' It also directs users to 'Just use filters' to narrow down, but it doesn't explicitly mention when to prefer get_job or list_filters, limiting the alternative differentiation.

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

All Jobs Base 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.2/5.0
Disambiguation5/5

Each tool has a distinct purpose: search_jobs finds listings, list_filters discovers filter options, and get_job retrieves full details. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: search_jobs, list_filters, get_job.

Tool Count5/5

Three tools are well-scoped for a job board: search, filter discovery, and detail retrieval. No extraneous or missing core functionality.

Completeness5/5

The tool set covers the full workflow: discover filters, search with filters, and get details. No obvious gaps for a read-only job board.

Resources