Resume Booster Job Board

Did this employer's board grow?

employer_growth

Read-onlyIdempotent

Did this employer's board serve more roles than 7 days earlier? One row per companyToken (up to 20 a call), judged by the board from our own daily observation and passed through untouched: grew, no-growth, or unknown, and unknown ALWAYS carries unknown_reason (a reading we could not take, never a no). The bars: at least 10 roles served at the start; then BOTH 4 more roles AND 25% more, on a board tracked for at least 21 days, every read in the window whole. Per board, never summed; not a headcount and not a hire. This tool never ranks employers, and no list of growing employers exists here or anywhere on the board.

Input Schema

Name	Required	Description	Default
`companyTokens`	Yes	companyToken values from job cards or search_jobs. Up to 20; more is refused with the count named.

Output Schema

Name	Required	Description	Default
`bars`	Yes
`asked`	No
`basis`	Yes
`employers`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 31, 2026

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

removedOutput schema / properties / bars / description

Removed value: -"What the verdict measured against — for reading a row, never for re-judging one."

removedOutput schema / properties / employers / description

Removed value: -"One row per token asked, in the order asked. A token with no daily series answers unknown with its reason."

removedOutput schema / properties / employers / items / additionalProperties
```
Removed value: -true
```
removedOutput schema / properties / employers / items / properties / baseline_day / description
```
Removed value: -"Our observation date at the window's start."
```
removedOutput schema / properties / employers / items / properties / baseline_served / description
```
Removed value: -"Roles served on this board on baseline_day."
```
removedOutput schema / properties / employers / items / properties / board_days_ok / description
```
Removed value: -"Days in the read-quality ledger whose read of this board was whole."
```
removedOutput schema / properties / employers / items / properties / latest_day / description
```
Removed value: -"Our latest observation date."
```

removedOutput schema / properties / employers / items / properties / net / description

Removed value: -"latest_served minus baseline_served: roles opened net of roles that came down. Not a headcount."

removedOutput schema / properties / employers / items / properties / rate / description

Removed value: -"net over baseline_served. Null when the baseline is zero or unread."

removedOutput schema / properties / employers / items / properties / tenure_censored / description

Removed value: -"True when the board is as old as the series itself, so its real tenure is longer than we can say."

removedOutput schema / properties / employers / items / properties / tenure_days / description
```
Removed value: -"Days between the board's first daily observation and the window's start."
```

removedOutput schema / properties / employers / items / properties / unknown_reason / description

Removed value: -"Null for grew and no-growth. Otherwise the gate that refused, in the migration's own words."

removedOutput schema / properties / employers / items / properties / untracked_departures / description
```
Removed value: -"OUR removals over the window — never counted as the employer shrinking."
```

removedOutput schema / properties / employers / items / properties / verdict / description

Removed value: -"The board's own judgement, passed through untouched. unknown is NOT no-growth: it is a reading we could not take, and unknown_reason says why."

First observedSep 18, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: output categories, guaranteed unknown_reason for unknowns, minimum thresholds, tracking duration, and the rule that results are per board and never summed. This is rich transparency for a read-only, idempotent tool whose annotations already cover safety.

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 front-loads the core question and then layers constraints in a logical order. It is somewhat dense and repetitive in places, but most sentences carry semantic weight about thresholds, unknowns, and non-ranking behavior.

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 output schema, annotations, and fully documented parameter, the description supplies everything an agent needs to understand the metric, its thresholds, and its limitations. Return-value structure can be left to the output schema.

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 the single companyTokens parameter is already well documented. The description adds that there is one row per companyToken and reinforces the 20-token limit, but does not add syntax or format details beyond the schema.

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 clearly states the specific measurement: whether an employer's board served more roles than 7 days earlier, with grew/no-growth/unknown outcomes. It also distinguishes the metric from headcount and hires, though it does not explicitly name sibling tools like employer_hiring_record or board_stats.

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 question and by exclusions such as 'never ranks employers' and 'no list of growing employers exists,' which tell the agent what not to expect. However, it does not explicitly say when to choose this tool over alternatives such as employer_hiring_record or board_stats.

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.