Skip to main content
Glama

SteadyScrape Jobs Data

Remote jobs by where you can work

remote_jobs
Read-only

Remote jobs from company career boards, filtered by the countries, regions or time zone the employer accepts: title, company, remote type, eligible countries and regions, seniority, salary when published, posting date and job URL. Billed per job returned.

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

Input Schema

NameRequiredDescriptionDefault
limitNoJobs to return in total (default 20, max 50). Billed per job returned.
regionsNoOptional: e.g. Europe, EMEA, LATAM, North America.
keywordsNoOptional title keywords, e.g. "backend", "product designer". Empty = all remote jobs.
seniorityNoOptional: e.g. JUNIOR, MID, SENIOR, LEAD.
worker_timezoneNoOptional: your UTC offset, e.g. UTC-6 or +5:30; keeps jobs within 3 hours.
worker_countriesNoOptional: only jobs open to workers in these countries (ISO codes or names, or EU).
posted_within_daysNoOnly jobs posted in the last N days (default 14).
include_descriptionsNoInclude the first 1,500 characters of each description as plain text (default false). Not billed extra.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive behavior, so the description's main contribution is the cost model: "Billed per job returned," reinforced in the limit parameter and the note that descriptions are not billed extra. That is genuinely useful pre-invocation context an agent cannot get from annotations. It still says nothing about result ordering or how partial eligibility matches behave.

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?

Two sentences: the field summary first, the billing caveat second. It is dense but front-loaded and nothing is redundant with siblings-restating filler. The long field list is somewhat run-on but each item earns its place by signaling what comes back.

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?

For an 8-parameter, all-optional filter tool with no output schema, the definition covers purpose, returned fields, defaults and cost. The remaining gap is behavioral edge cases (no filters, partial timezone matches), which are minor and partly handled by the schema itself.

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 coverage is 100%, so every parameter is already documented with examples and bounds, making 3 the baseline. The description adds little beyond the schema apart from framing the region/country filters as employer eligibility, which is a small semantic clarification, not new information.

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?

The description states a specific resource (remote jobs from company career boards) and its distinguishing scope (filtered by countries, regions or time zone the employer accepts), plus an enumeration of returned fields. It is clear what the tool does, though it never names or contrasts with siblings like search_jobs or company_jobs.

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

Usage Guidelines3/5

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

Usage is implied by the scoping clause: use this when you want remote roles filtered by where the employer will hire. There is no explicit when-to-use versus alternatives, no statement of when not to use it, and no mention of the sibling tools that might overlap.

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