Skip to main content
Glama

SteadyScrape Jobs Data

Open jobs at specific companies

company_jobs
Read-only

Current open roles from 1-5 company career boards, read live from the board: title, department, location, remote flag, employment type, salary when published, posting date and job URL. Give board URLs (e.g. https://job-boards.greenhouse.io/stripe, https://jobs.lever.co/acme) or platform:slug (greenhouse:stripe). Billed per job returned.

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": {
      "companies": "<companies>"
    },
    "name": "company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoJobs to return in total (default 20, max 50). Billed per job returned.
keywordsNoOptional: keep jobs whose title contains any of these.
companiesYes1-5 career board URLs or platform:slug values.
locationsNoOptional: city, region or country names or ISO codes.
remote_onlyNoOnly remote jobs (default false).
posted_within_daysNoOnly jobs posted in the last N days.
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 already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so what counts is added context: the data is "read live from the board" (freshness, no cached/stale results) and "Billed per job returned" (a real cost constraint, repeated twice, consistent with idempotentHint=false). It doesn't cover failure behavior for invalid boards, which keeps it below 5.

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 front-loaded sentences: capability and returned fields first, input format second, billing last. Every sentence carries information an agent needs, and the example URLs cost little for the ambiguity they remove.

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 correctly enumerates the return fields, and it discloses freshness and per-job billing for a 7-parameter tool whose schema is fully documented. What's absent is edge-case behavior (invalid or unreachable boards, partial results across 5 boards), a minor gap rather than a blocking one.

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 baseline is 3; the description goes beyond the terse schema wording by giving concrete identifier examples (https://job-boards.greenhouse.io/stripe, greenhouse:stripe), which materially reduces malformed-input risk for the required companies parameter. It adds no further meaning for limit, keywords, locations, remote_only, or posted_within_days.

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 and resource ("Current open roles from 1-5 company career boards") plus the exact field set returned (title, department, location, remote flag, employment type, salary, posting date, URL). Scope is bounded at 1-5 boards, which is enough for an agent to distinguish this from a broad search tool like search_jobs without opening a schema.

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 context is implied: use when you have specific company career-board identifiers. It explains the accepted identifier formats (board URLs, platform:slug) but never states when NOT to use it or when a sibling such as search_jobs or remote_jobs is the better choice.

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