Skip to main content
Glama

Hiring Signals

Fastest-hiring companies in a segment

segment_hiring_ranking
Read-onlyIdempotent

Best for: who is hiring fastest in a market, such as "which companies added the most sales roles in Berlin this week?". Returns: companies ranked by new roles over 7 days, each with boards, open roles, baseline weekly average, ratio and a spike flag, plus as_of and the method. Input tips: {"segment": {"function": "sales", "city": "berlin"}}, {"segment": {"ats": ["greenhouse"]}} or {"segment": {"companies": ["stripe.com"]}}; no segment ranks every company. A function or city segment is this week's leaderboard list (at most 50). Country and size are not filters. Needs: an API key with segment access; else subscription_required. Not for: one company's detail (use company_hiring_brief).

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": {
      "limit": 20,
      "segment": {
        "ats": [
          "greenhouse"
        ]
      }
    },
    "name": "segment_hiring_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCompanies to return, fastest first. Default 50.
segmentNoWhich companies to rank. Leave it out to rank every company the history store reads.

Output Schema

NameRequiredDescriptionDefault
as_ofYesISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
methodYes
sourceYesWho the data comes from, to cite and to check it against.
segmentYes
companiesYes
thresholdsNo
api_versionYesDate of this answer's shape; it changes only when a field is removed or changes meaning.
plan_active_untilNo
unavailable_filtersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds an access requirement the annotations don't: it needs an API key with segment access or returns subscription_required. It also discloses that function/city segments return a capped leaderboard (at most 50) and that results carry as_of and a method field, which is real behavioral context beyond the structured fields.

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 labeled structure (Best for / Returns / Input tips / Needs / Not for) is front-loaded and scannable, with no filler sentences. The example segment objects partially duplicate the schema's own examples, which is the only mild redundancy.

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 two-parameter nested tool with an output schema, this covers what an agent still needs: the ranking basis (7-day window), the cap on leaderboard segments, the auth precondition and its failure mode, and the correct sibling for a different intent. Nothing material to calling it correctly is missing.

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 description coverage is already 100%, so the baseline is 3, but the description exceeds that by explaining interactions the schema leaves implicit: no segment ranks every company, function or city yields this week's capped leaderboard, and country/size are explicitly not filters. Those negative constraints and combination rules add genuine meaning beyond the per-property text.

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 gives a concrete verb and resource: it ranks companies by new roles over 7 days, with a leaderboard-style question as an example ("which companies added the most sales roles in Berlin this week?"). It also explicitly names the sibling it is not, company_hiring_brief, so an agent can tell it apart 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 Guidelines5/5

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

It includes an explicit "Best for" statement of the question type it answers and a "Not for" that routes one-company detail to company_hiring_brief. It even shows which segment shapes are valid (function+city, ats, companies) and notes that omitting segment ranks every company, so the agent knows when each form applies.

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.