Resume Booster Job Board

An employer's hiring record on this board

employer_hiring_record

Read-onlyIdempotent

For each employer handle (companyToken, up to 20 a call), its record on this board: open_roles, closed_90d (takedowns watched in 90 days, re-lists excluded), superseded_90d (re-lists, a floor), two medians from the employer's stated dates (lower bounds), tracking_days and feed_total. A takedown is not a hire — a filled role, a cancelled one and a withdrawn one look identical from here — and it is a record of one BOARD, never summed across an employer's boards, never a headcount. A board with no closure observed answers record:'unknown' with its reason, never a verdict about the employer: on a board bigger than one visit can read, no closure is observable to us until we complete a provable full pass and then watch a role go after it. Every row carries its basis. Every row also carries layoff_filing, the newest US state WARN notice or SEC 8-K Item 2.05 disclosure matched to the employer by a curated alias or an exact multi-token name, printed as a filing (filer verbatim, dates with their bases, count, state or form, link), read hourly from SEC EDGAR and nightly from state notices, null when none qualifies within 90 days, and no part of any verdict; layoff_basis says what it is and is not. Pair with employer_growth for the other half of what the site calls "Actively hiring".

Input Schema

Name	Required	Description	Default
`companyTokens`	Yes	companyToken values from job cards or search_jobs (a vendor tenant, e.g. 'acme' or 'gici~wd5~Careers'). Up to 20; more is refused with the count named.

Output Schema

Name	Required	Description	Default
`asked`	No
`basis`	Yes
`employers`	Yes
`layoff_read`	Yes
`window_days`	No
`layoff_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedOct 31, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

removedOutput schema / properties / employers / description

Removed value: -"One row per token asked, in the order asked. A token the board does not carry still answers, as unknown."

removedOutput schema / properties / employers / items / additionalProperties
```
Removed value: -true
```

removedOutput schema / properties / employers / items / properties / closed_90d / description

Removed value: -"Watched takedowns in the window, re-lists excluded. Never a count of hires."

removedOutput schema / properties / employers / items / properties / feed_total / description

Removed value: -"What the employer's feed advertised at the last verification. Null when never verified."

changedOutput schema / properties / employers / items / properties / layoff_filing / additionalProperties
```
Previous value: -falseNew value: +true
```

removedOutput schema / properties / employers / items / properties / layoff_filing / description

Removed value: -"The newest qualifying layoff filing joined to this employer, or null when none qualifies. A fact about the employer on one date, beside the record and no part of it."

removedOutput schema / properties / employers / items / properties / layoff_filing / properties

Removed value: -{
-  "effective_date": {
-    "description": "The date the WARN notice gives for the separations; null when it gives none or on an SEC filing.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "event_basis": {
-    "type": "string"
-  },
-  "event_date": {
-    "description": "The filing's own date: the WARN notice date or the 8-K report date. Named by event_basis.",
-    "type": "string"
-  },
-  "event_type": {
-    "description": "What the WARN notice says it is, as the state classifies it; null on an SEC filing.",
-    "enum": [
-      "closure",
-      "layoff",
-      "relocation",
-      "unknown",
-      null
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "filer": {
-    "description": "The employer as the source names it, verbatim — never the board's own display name.",
-    "type": "string"
-  },
-  "form": {
-    "description": "The SEC form (an amendment never appears); null on a WARN notice.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "headcount": {
-    "description": "Positions the 8-K states, as parsed; null when it states none or on a WARN notice.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  },
-  "more_n": {
-    "description": "Further qualifying filings for this employer beyond this newest one.",
-    "type": "integer"
-  },
-  "pct": {
-    "description": "Workforce share the 8-K states, as parsed; null when it states none or on a WARN notice.",
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "public_basis": {
-    "type": "string"
-  },
-  "public_date": {
-    "description": "When it became public: the SEC file date or the state's received/processed/posted stamp. Named by public_basis.",
-    "type": "string"
-  },
-  "read_at": {
-    "description": "When we read it. Our stamp, never a date basis for the filing.",
-    "type": "string"
-  },
-  "relation": {
-    "description": "filer: the filer is this board's employer. subsidiary_site: the filer is the parent company of this board's employer.",
-    "enum": [
-      "filer",
-      "subsidiary_site"
-    ],
-    "type": "string"
-  },
-  "site": {
-    "description": "The notice's site as the state lists it; null when not stated or on an SEC filing.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "source": {
-    "description": "state_warn: a US state WARN notice. sec_8k_205: an SEC 8-K Item 2.05 disclosure.",
-    "enum": [
-      "sec_8k_205",
-      "state_warn"
-    ],
-    "type": "string"
-  },
-  "source_name": {
-    "description": "SEC EDGAR, or the state agency as it names itself.",
-    "type": "string"
-  },
-  "source_url": {
-    "description": "The filing itself, at the source.",
-    "type": "string"
-  },
-  "state": {
-    "description": "Two-letter state of a WARN notice; null on an SEC filing.",
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "workers": {
-    "description": "Positions the WARN notice states at that site. Null on an SEC filing — never zero.",
-    "type": [
-      "integer",
-      "null"
-    ]
-  }
-}

removedOutput schema / properties / employers / items / properties / layoff_filing / required

Removed value: -[
-  "source",
-  "relation",
-  "filer",
-  "event_date",
-  "event_basis",
-  "public_date",
-  "public_basis",
-  "state",
-  "site",
-  "workers",
-  "event_type",
-  "effective_date",
-  "pct",
-  "headcount",
-  "form",
-  "source_url",
-  "source_name",
-  "read_at",
-  "more_n"
-]

removedOutput schema / properties / employers / items / properties / median_days_open / description

Removed value: -"Median age of the roles served now, from the employer's stated dates only. Null when none carry one."

removedOutput schema / properties / employers / items / properties / median_days_to_close / description

Removed value: -"Median stated-date-to-takedown over the window's dated closures. A lower bound; null when no closure carries a date."

removedOutput schema / properties / employers / items / properties / note / description

Removed value: -"Present on an unknown row: what the absence means and does not mean."

removedOutput schema / properties / employers / items / properties / open_roles / description

Removed value: -"Postings served from this board right now, under the same two serving rules as search."

removedOutput schema / properties / employers / items / properties / record / description

Removed value: -"observed: the ledger holds at least one closure for this board in the window, so the figures speak. unknown: it holds none, with unknown_reason saying why that is not a finding."

removedOutput schema / properties / employers / items / properties / superseded_90d / description
```
Removed value: -"Re-lists in the window — a FLOOR, one logged per title per day."
```
removedOutput schema / properties / employers / items / properties / tracking_days / description
```
Removed value: -"Days this board has been watched, capped."
```

removedOutput schema / properties / layoff_basis / description

Removed value: -"What layoff_filing is and is not, beside every row's record."

removedOutput schema / properties / layoff_read / description

Removed value: -"\"ok\" when the filing reader answered for every employer; otherwise \"unread: <fault>\" and every layoff_filing on this response is null for that reason, never because nothing qualified. The record is unaffected either way."

Changed5 schema fields changedSep 18, 2026

addedOutput schema / properties / employers / items / properties / layoff_filing

Added value: +{
+  "additionalProperties": false,
+  "description": "The newest qualifying layoff filing joined to this employer, or null when none qualifies. A fact about the employer on one date, beside the record and no part of it.",
+  "properties": {
+    "effective_date": {
+      "description": "The date the WARN notice gives for the separations; null when it gives none or on an SEC filing.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "event_basis": {
+      "type": "string"
+    },
+    "event_date": {
+      "description": "The filing's own date: the WARN notice date or the 8-K report date. Named by event_basis.",
+      "type": "string"
+    },
+    "event_type": {
+      "description": "What the WARN notice says it is, as the state classifies it; null on an SEC filing.",
+      "enum": [
+        "closure",
+        "layoff",
+        "relocation",
+        "unknown",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "filer": {
+      "description": "The employer as the source names it, verbatim — never the board's own display name.",
+      "type": "string"
+    },
+    "form": {
+      "description": "The SEC form (an amendment never appears); null on a WARN notice.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "headcount": {
+      "description": "Positions the 8-K states, as parsed; null when it states none or on a WARN notice.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "more_n": {
+      "description": "Further qualifying filings for this employer beyond this newest one.",
+      "type": "integer"
+    },
+    "pct": {
+      "description": "Workforce share the 8-K states, as parsed; null when it states none or on a WARN notice.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "public_basis": {
+      "type": "string"
+    },
+    "public_date": {
+      "description": "When it became public: the SEC file date or the state's received/processed/posted stamp. Named by public_basis.",
+      "type": "string"
+    },
+    "read_at": {
+      "description": "When we read it. Our stamp, never a date basis for the filing.",
+      "type": "string"
+    },
+    "relation": {
+      "description": "filer: the filer is this board's employer. subsidiary_site: the filer is the parent company of this board's employer.",
+      "enum": [
+        "filer",
+        "subsidiary_site"
+      ],
+      "type": "string"
+    },
+    "site": {
+      "description": "The notice's site as the state lists it; null when not stated or on an SEC filing.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "description": "state_warn: a US state WARN notice. sec_8k_205: an SEC 8-K Item 2.05 disclosure.",
+      "enum": [
+        "sec_8k_205",
+        "state_warn"
+      ],
+      "type": "string"
+    },
+    "source_name": {
+      "description": "SEC EDGAR, or the state agency as it names itself.",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "The filing itself, at the source.",
+      "type": "string"
+    },
+    "state": {
+      "description": "Two-letter state of a WARN notice; null on an SEC filing.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "workers": {
+      "description": "Positions the WARN notice states at that site. Null on an SEC filing — never zero.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "source",
+    "relation",
+    "filer",
+    "event_date",
+    "event_basis",
+    "public_date",
+    "public_basis",
+    "state",
+    "site",
+    "workers",
+    "event_type",
+    "effective_date",
+    "pct",
+    "headcount",
+    "form",
+    "source_url",
+    "source_name",
+    "read_at",
+    "more_n"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / properties / employers / items / required

Previous value: -[
-  "company_token",
-  "record",
-  "basis"
-]New value: +[
+  "company_token",
+  "record",
+  "basis",
+  "layoff_filing"
+]

addedOutput schema / properties / layoff_basis

Added value: +{
+  "description": "What layoff_filing is and is not, beside every row's record.",
+  "type": "string"
+}

addedOutput schema / properties / layoff_read

Added value: +{
+  "description": "\"ok\" when the filing reader answered for every employer; otherwise \"unread: <fault>\" and every layoff_filing on this response is null for that reason, never because nothing qualified. The record is unaffected either way.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "employers",
-  "basis"
-]New value: +[
+  "employers",
+  "basis",
+  "layoff_basis",
+  "layoff_read"
+]

First observedSep 18, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, open-world behavior, and the description adds substantial context beyond them: takedowns are not hires, results are per-board and never summed, unknown records carry reasons, rows carry their basis, and layoff filings have explicit source, matching, freshness, null, and verdict-disclaimer semantics.

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?

The description is dense and long, but it is front-loaded with the returned fields and every caveat is relevant to correct interpretation. Some sentences could be split or tightened, yet there is little outright waste.

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?

Given the complex output semantics and the existence of an output schema, the description is complete enough for correct use: it explains data provenance, freshness, matching rules, null behavior, per-board limitations, and how to pair the tool with employer_growth.

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% for the single parameter, so the schema already documents companyToken source, maxItems 20, and refusal behavior. The description reinforces that companyToken is an employer handle and repeats the 20-item limit, but adds limited meaning beyond the schema.

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?

The description states a specific resource and scope: per employer handle, the record on this board, with named fields like open_roles, closed_90d, superseded_90d, medians, tracking_days and feed_total. It also distinguishes the data from headcounts and from employer_growth, so an agent can identify the tool 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 Guidelines3/5

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

It names employer_growth as a complementary tool for the other half of 'Actively hiring,' which gives some usage context. However, it does not explicitly say when to choose this tool over siblings such as board_stats or check_jobs_open, nor does it state when not to use it.

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

All Resume Booster Job Board tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.