webdata-tools-mcp

Get all open jobs from company career pages

get_company_jobs

Read-onlyIdempotent

Extract open jobs from company career page URLs into one normalized format with title, location, seniority, salary, and apply links. Filters results by remote work, location, posting date, or job title.

Instructions

All open jobs from company career pages in one normalized format (title, company, location, remote/hybrid, seniority, salary, apply URL, posted date). Paste career-page URLs from Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Workday, Personio or Teamtailor; the board type is detected automatically. Runs the Apify Actor tacps126/jobs-harvester on your Apify account (about $0.001 per job; spend per call is capped at $0.5).

Input Schema

TableJSON Schema

Name	Required	Description
`max_items`	No	Maximum results to return (default 50, max 500). Cost scales with this.
`extra_input`	No	Advanced: extra Actor input fields, merged over the defaults.
`remote_only`	No	Only remote jobs.
`title_includes`	No	Keep jobs whose title contains any of these.
`career_page_urls`	Yes	Career page URLs, e.g. "https://jobs.lever.co/spotify".
`location_includes`	No	Keep jobs in these locations.
`posted_within_days`	No	Only jobs posted in the last N days.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	Name of the tool that produced the result.
`count`	Yes	Number of records the Actor returned.
`items`	Yes	The records. Long text fields are shortened to 600 characters.
`shown`	Yes	Number of records included in `items` (can be lower than count when the result is long).
`truncated`	Yes	True when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Oct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Number of records the Actor returned.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records. Long text fields are shortened to 600 characters.",
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shown": {
+      "description": "Number of records included in `items` (can be lower than count when the result is long).",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "tool": {
+      "description": "Name of the tool that produced the result.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when records were left out to keep the result short; ask for fewer items.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "count",
+    "shown",
+    "truncated",
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint). The description adds genuinely new context beyond them: the tool runs the Apify Actor tacps126/jobs-harvester on the user's Apify account, costs about $0.001 per job, and spend is capped at $0.5 per call. That cost/ownership disclosure is exactly the kind of extra behavioral value that matters here.

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 dense sentences that are front-loaded with the outcome, then the input format, then the cost model; nothing is redundant. It is slightly list-heavy but every clause earns its place.

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 a scraper with a full input schema, output schema, and annotations covering the safety profile, the description adds the missing operational context (provider support, auto-detection, cost and per-call cap). Only the explicit when-to-use-this-versus-siblings guidance is absent, which keeps it just shy of complete.

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% and an output schema exists, so the schema already documents all 7 parameters including defaults, ranges and cost scaling. The description adds no parameter-specific syntax or format detail beyond what the schema provides, so the baseline 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 (get) and resource (all open jobs from company career pages) and names the nine supported board providers. It also enumerates the normalized output fields, which clearly separates it from siblings like search_indeed_jobs and find_hiring_companies without opening either 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 clear operational context: paste career-page URLs from a specific list of ATS providers and the board type is auto-detected, which tells the agent exactly what input this tool expects. However, it never explicitly contrasts itself against alternatives such as search_indeed_jobs or find_hiring_companies, so the choice between them is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server