Skip to main content
Glama

Hiring Signals

Company hiring brief

company_hiring_brief
Read-onlyIdempotent

Best for: what one company is hiring for and how fast, such as "what is Snap hiring for?" or "is Airbnb hiring faster this month?". Returns: open roles, shares remote and with a salary, top departments and countries, the 5 newest roles, and roles opened and closed over 7, 30 and 90 days and per week once the board has a day of history. The board token goes into watch_new_roles. Input tips: {"company": "https://snapchat.wd1.myworkdayjobs.com/snap"}, an "ats:slug" token or a company name. Not for: lists of individual jobs with filters, or people at the company.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "greenhouse:airbnb"
    },
    "name": "company_hiring_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesA careers page URL, an "ats:slug" token such as "greenhouse:airbnb", or a company name or domain such as "stripe.com".

Output Schema

NameRequiredDescriptionDefault
atsYes
noteYes
as_ofYesISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
boardYesThe ats:slug token; pass it to watch_new_roles to follow this board.
newestYes
sourceYesWho the data comes from, to cite and to check it against.
weeklyNoRoles opened and closed per week (Monday dates, oldest first, up to 13), for boards the history store reads daily.
companyYes
velocityYesRoles opened and closed over each window (7, 30 and, from the history store, 90 days), from daily reads of this board; a window starts no earlier than the first read, and the list is empty until the board has a day of history.
countriesYes
open_rolesYes
api_versionYesDate of this answer's shape; it changes only when a field is removed or changes meaning.
departmentsYes
history_daysYesDays of history kept for this board.
remote_shareNoShare of open roles marked remote, 0 to 1.
salary_shareNoShare of open roles that publish a salary, 0 to 1.
hiring_velocityNoNot in every answer. New roles per ISO week (Monday dates) for the company's tracked boards, each role once on the day its board says it was posted (Greenhouse, Lever, Ashby) or first seen: the last 7 days, the 4 newest weeks, 13 weeks, a trend and the percentile among tracked companies. Counts only roles still open or seen since the board was first read. Null when the history store does not track the board.
untrusted_sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / hiring_velocity / description
      Previous value: -"Paid calls only. New roles per ISO week (Monday dates) for the company's tracked boards, each role once on the day its board says it was posted (Greenhouse, Lever, Ashby) or first seen: the last 7 days, the 4 newest weeks, 13 weeks, a trend and the percentile among tracked companies. Counts only roles still open or seen since the board was first read. Null when the history store does not track the board."New value: +"Not in every answer. New roles per ISO week (Monday dates) for the company's tracked boards, each role once on the day its board says it was posted (Greenhouse, Lever, Ashby) or first seen: the last 7 days, the 4 newest weeks, 13 weeks, a trend and the percentile among tracked companies. Counts only roles still open or seen since the board was first read. Null when the history store does not track the board."
    • removedOutput schema / properties / hiring_velocity_hint
      Removed value: -{
      -  "description": "Present instead of hiring_velocity on a call that was not paid: how to get it.",
      -  "type": "string"
      -}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / hiring_velocity
      Added value: +{
      +  "description": "Paid calls only. New roles per ISO week (Monday dates) for the company's tracked boards, each role once on the day its board says it was posted (Greenhouse, Lever, Ashby) or first seen: the last 7 days, the 4 newest weeks, 13 weeks, a trend and the percentile among tracked companies. Counts only roles still open or seen since the board was first read. Null when the history store does not track the board.",
      +  "properties": {
      +    "as_of": {
      +      "type": "string"
      +    },
      +    "boards": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "history": {
      +      "enum": [
      +        "backfilled",
      +        "since_first_read"
      +      ],
      +      "type": "string"
      +    },
      +    "label": {
      +      "type": "string"
      +    },
      +    "last_4_weeks": {
      +      "items": {
      +        "properties": {
      +          "new": {
      +            "type": "integer"
      +          },
      +          "week": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "week",
      +          "new"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "method": {
      +      "type": "string"
      +    },
      +    "new_last_7_days": {
      +      "type": "integer"
      +    },
      +    "percentile": {
      +      "description": "0 to 100: the share of tracked companies with fewer new roles in their 4 newest weeks.",
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "ranked_companies": {
      +      "type": "integer"
      +    },
      +    "trend": {
      +      "enum": [
      +        "rising",
      +        "steady",
      +        "falling",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "weeks": {
      +      "items": {
      +        "properties": {
      +          "new": {
      +            "type": "integer"
      +          },
      +          "week": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "week",
      +          "new"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / hiring_velocity_hint
      Added value: +{
      +  "description": "Present instead of hiring_velocity on a call that was not paid: how to get it.",
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedOutput schema / properties / history_days / description
      Previous value: -"Days of snapshots kept for this board."New value: +"Days of history kept for this board."
    • changedOutput schema / properties / velocity / description
      Previous value: -"Roles opened and closed over each window, from daily snapshots of this board; empty until the board has history that old."New value: +"Roles opened and closed over each window (7, 30 and, from the history store, 90 days), from daily reads of this board; a window starts no earlier than the first read, and the list is empty until the board has a day of history."
    • addedOutput schema / properties / weekly
      Added value: +{
      +  "description": "Roles opened and closed per week (Monday dates, oldest first, up to 13), for boards the history store reads daily.",
      +  "items": {
      +    "properties": {
      +      "closed": {
      +        "type": "integer"
      +      },
      +      "opened": {
      +        "type": "integer"
      +      },
      +      "week": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "week",
      +      "opened",
      +      "closed"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the exact output dimensions (remote/salary shares, top departments and countries, 5 newest roles) and a data-maturity caveat that per-week stats only appear once the board has a day of history. It stops short of covering failure modes or unknown-company handling.

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?

Labeled sections (Best for / Returns / Input tips / Not for) make it skimmable and front-loaded with the decisive information. The Returns sentence is a dense run-on enumeration that is informative but heavier than it needs to be.

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?

For a single-parameter read tool with an output schema and full annotation coverage, nothing an agent needs is missing: it knows the input formats, what comes back, when stats become available, and where the derived token is reused.

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 the single parameter already documents URL, "ats:slug" token, and company name/domain forms, so baseline 3 applies. The "Input tips" line adds one concrete raw careers-page URL example not present in the schema, which is a marginal gain rather than meaningful new semantics.

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: what one company is hiring for and how fast, with concrete user-style phrasings ("what is Snap hiring for?"). It explicitly excludes the closest sibling behavior (filtered lists of individual jobs) so the agent can discriminate 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 Guidelines5/5

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

Provides explicit "Best for" and "Not for" sections plus a forward reference: the board token it yields is the input to watch_new_roles. That is when-to-use, when-not-to-use, and sibling routing in one place.

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.