Skip to main content
Glama

SteadyScrape Jobs Data

Get results of a longer job search

get_results
Read-onlyIdempotent

Fetch the results of a company_jobs, search_jobs or remote_jobs call that returned a run_id because it took longer than about two minutes. Returns the status while it is still running. Free: the original run is billed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "run_id": "<run_id>"
    },
    "name": "get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoJobs to return (default all, up to 55).
run_idYesThe run_id from the earlier call.
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

A4.2/5.0
Behavior4/5

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

Annotations cover read-only, idempotent, non-destructive and open-world traits, and the description adds genuinely new behavior: it returns status while the job is still running (i.e., polling semantics) and it is free because the original run is billed. It does not state result expiry, polling cadence, or what a still-running response looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then the polling behavior, then the billing note. No filler and every sentence carries information an agent needs.

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 no output schema, the description covers enough to call the tool correctly and signals that responses can be a pending status rather than finished jobs. The exact shape of a successful result (job list, pagination beyond limit) is left implicit, a minor gap for a low-complexity 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 run_id, limit and include_descriptions are already fully documented in the schema, including the 55-job cap and the no-extra-cost note. The description adds nothing about these parameters, so the baseline of 3 applies.

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 specific verb (fetch) and resource (results) and precisely scopes it to a run_id produced by company_jobs, search_jobs or remote_jobs. The title and description together let an agent distinguish it from the sibling search tools without opening the schema.

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?

Gives a clear triggering condition: use it after one of the three named search calls returned a run_id because it exceeded about two minutes. It does not explicitly state the negative case (do not call it without a run_id) or how often to poll, but the context is unambiguous.

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