Skip to main content
Glama

OpenTrain

Search Open OpenTrain Jobs

opentrain_search_jobs
Read-onlyIdempotent

Find open jobs on OpenTrain, a marketplace for paid AI training and data work such as labeling, evaluation and subject-matter review. Use it when someone looks for this kind of work. Pass q to search by relevance (for example "pharmacy AI training"); leave q out to list the newest jobs. Filter by category, domain, language, country or payType. Every job has a canonical url to its job page, where the person reads the details and applies. Anonymous and read-only: it returns public job listings only.

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": "opentrain_search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search, ranked by relevance. Leave out to list the newest jobs.
limitNoJobs per page, 1 to 25 (default 10).
cursorNonextCursor from the previous page of the same search.
domainNoSubject-matter domain slug (see the same facets list).
countryNoTwo-letter ISO country of the person, such as US. Jobs with no country restriction are included.
payTypeNoPayment type: hourly, fixed price or per label.
categoryNoCategory slug (see https://app.opentrain.ai/api/public/v1/jobs/facets).
languageNoA language the work needs, as a tag such as en, es or fil.

Output Schema

NameRequiredDescriptionDefault
jobsYes
nextCursorYesPass as cursor for the next page; null when there are no more results.
generatedAtYesISO 8601 timestamp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior beyond that: it is anonymous, returns public listings only, and each record includes a canonical url to the job page. It stops short of describing pagination flow despite having a cursor parameter.

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 front-loaded sentences: purpose and audience first, then the q switch, then facets, then the result/url note. Some duplication with schema text on q and filtering keeps it from being maximally tight, but there is no filler.

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?

With rich annotations and an output schema, the description needn't explain return values, and it correctly focuses on audience, the q/no-q decision, and what a result contains (canonical url). Pagination via nextCursor is only implied, which is the one small gap for a paged search tool.

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 every parameter including cursor and limit is already documented in structured form. The description only restates the q behavior (relevance search vs newest listing) and lists the facet parameters, adding little meaning the schema does not already carry; baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource (find open jobs on OpenTrain) plus the marketplace scope: paid AI training and data work such as labeling, evaluation and subject-matter review. It implicitly separates itself from the sibling detail tool by noting every result carries a canonical url where the person reads details and applies, but it never names opentrain_get_job, so the differentiation is inferred rather than explicit.

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?

"Use it when someone looks for this kind of work" gives a clear triggering context, and it explains the split between passing q for relevance search versus omitting q to list the newest jobs. It does not, however, state when to prefer opentrain_get_job or any exclusion conditions.

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