Skip to main content
Glama

roTEAMnet — Global Job Search & Employer Discovery

search_jobs

Read-onlyIdempotent

Search active, unexpired catalogue jobs, excluding jobs hidden by this account. Returns total, page, pages and up to 24 jobs, newest first; zero matches returns jobs=[] and page=pages=1. Filters combine with AND. No AI, credit charge, save or application submission. Use get_job for full posting text and eligibility, get_market for aggregate counts. Counts may be cached; jobs can expire between calls. Required scope: jobs:read

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
qNoOptional keywords matched against job title, employer, skills and categories. Use concise terms such as PHP; this is keyword search, not semantic matching. Omit for all jobs.
modeNoOptional workplace arrangement. Remote does not mean worldwide eligibility; read each posting.
pageNoOne-based page, default 1. Up to 24 jobs per page, newest first. Out-of-range pages clamp to the last page. Check returned page/pages; stop when page equals pages.
timingNoOptional declared time of work. Unknown timing does not satisfy a specified filter.
countryNoOptional ISO 3166-1 alpha-2 country, e.g. RO or DE. One country per call; omit for all countries. Does not represent citizenship or visa eligibility.
scheduleNoOptional declared schedule pattern; independent of workplace arrangement.
max_hoursNoOptional maximum declared weekly hours, inclusive, 1–80. Jobs with unknown weekly hours are excluded when supplied.
engagementNoOptional declared employment/engagement category. Combine with mode for remote part-time or contract searches.

Output Schema

NameRequiredDescriptionDefault
jobsYes
pageYes
pagesYes
totalYesMatching catalogue postings, possibly from a short-lived count cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / country / description
      Added value: +"Optional ISO 3166-1 alpha-2 country, e.g. RO or DE. One country per call; omit for all countries. Does not represent citizenship or visa eligibility."
    • addedInput schema / properties / engagement / description
      Added value: +"Optional declared employment/engagement category. Combine with mode for remote part-time or contract searches."
    • addedInput schema / properties / max_hours / description
      Added value: +"Optional maximum declared weekly hours, inclusive, 1–80. Jobs with unknown weekly hours are excluded when supplied."
    • addedInput schema / properties / mode / description
      Added value: +"Optional workplace arrangement. Remote does not mean worldwide eligibility; read each posting."
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / description
      Added value: +"One-based page, default 1. Up to 24 jobs per page, newest first. Out-of-range pages clamp to the last page. Check returned page/pages; stop when page equals pages."
    • addedInput schema / properties / q / description
      Added value: +"Optional keywords matched against job title, employer, skills and categories. Use concise terms such as PHP; this is keyword search, not semantic matching. Omit for all jobs."
    • addedInput schema / properties / schedule / description
      Added value: +"Optional declared schedule pattern; independent of workplace arrangement."
    • addedInput schema / properties / timing / description
      Added value: +"Optional declared time of work. Unknown timing does not satisfy a specified filter."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "jobs": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "company_name": {
      +            "description": "Published or configured employer name.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "description": "Catalogue identifier; pass as an integer to get_job.",
      +            "type": [
      +              "integer",
      +              "string"
      +            ]
      +          },
      +          "location": {
      +            "description": "Source location text; read restrictions in the full posting.",
      +            "type": "string"
      +          },
      +          "source_url": {
      +            "description": "Free original application URL.",
      +            "type": "string"
      +          },
      +          "title": {
      +            "description": "Employer-published job title.",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "roTEAMnet detail page.",
      +            "type": "string"
      +          },
      +          "work_options": {
      +            "description": "Declared flexible-work metadata; null or missing values mean unknown.",
      +            "type": [
      +              "object",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "maxItems": 24,
      +      "type": "array"
      +    },
      +    "page": {
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "pages": {
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "total": {
      +      "description": "Matching catalogue postings, possibly from a short-lived count cache.",
      +      "minimum": 0,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "page",
      +    "pages",
      +    "jobs"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: pagination shape (total, page, pages, up to 24 jobs, newest first), the zero-match edge case (jobs=[] and page=pages=1), AND-combination of filters, cache staleness on counts, expiry between calls, and the required jobs:read scope. These are exactly the behaviors an agent needs to avoid misinterpreting results.

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?

Front-loaded with purpose, then returns, filter semantics, alternatives, and caveats — no wasted preamble. Slightly dense in telegraphic fragments, and 'newest first' / pagination details partially restate the page parameter's schema description.

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?

An output schema exists, yet the description still covers the return envelope and the empty-result shape, plus staleness and auth scope. For an eight-parameter, zero-required filter tool, nothing an agent needs to call it correctly or interpret results is missing.

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 schema already carries per-parameter meaning and the enum caveats; baseline would be 3. The description adds one genuinely new semantic not in the schema: 'Filters combine with AND', which governs how the eight optional filters interact. That is real added value, but it is a single fact.

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 precise verb and resource ('Search active, unexpired catalogue jobs') plus the scope constraint ('excluding jobs hidden by this account'). Sibling functions are named with their distinct roles (get_job for posting text, get_market for aggregates), so an agent can route without opening any schema.

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 redirects to get_job and get_market with the conditions that select them, and rules out side effects ('No AI, credit charge, save or application submission') so the agent knows this is a safe, cheap discovery call. The 'jobs can expire between calls' note also tells the agent when to re-search rather than trust stale results.

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