signals

Find hiring signals

hiring_signals

Read-only

List hiring signals read from companies' own job boards, newest first: leadership openings, team build-outs, hiring surges and freezes, expansion into new countries and hard-to-fill roles. Each signal carries the roles behind it. Filter by type, function, seniority, company or a time window. Costs one credit per returned signal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hiring_signals"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum records to return (1-100). Each returned record costs one credit.
`since`	No	Return records announced on or after this date (YYYY-MM-DD) or ISO-8601 timestamp.
`until`	No	Return records announced on or before this date (YYYY-MM-DD, inclusive) or ISO-8601 timestamp.
`cursor`	No	Opaque pagination cursor returned as pagination.nextCursor on the previous page.
`domain`	No	Company domain, e.g. stripe.com. Matches the company's primary domain or any domain it redirected from; a full URL works too.
`function`	No	Job functions, e.g. sales or engineering. Canonical values: engineering, data, security, it, product, design, sales, marketing, customer_success, operations, finance, people, legal, research, healthcare, executive, other, all.
`companyId`	No	Filter by company id.
`countries`	No	Headquarters country codes (ISO alpha-2, OR). Pass "unknown" to include companies with no country on file.
`eventType`	No	Signal types. Canonical values: leadership_opening, founding_role, role_family_scaling, technology_hiring, team_buildout, hiring_surge, hiring_freeze, location_expansion, hard_to_fill, leadership_filled.
`seniority`	No	Seniority of a leadership opening, e.g. c_level, vp_level, head, director.
`activeOnly`	No	Only signals whose roles are still open.
`roleFamily`	No	Role families, e.g. sales_development, revops, security. Canonical values: sales_development, sales, sales_engineering, revops, gtm_engineering, partnerships, marketing, demand_gen, product_marketing, content_brand, customer_success, support, software_engineering, hardware_engineering, infrastructure, security, data_engineering, data_analytics, ml_ai, product_management, design, recruiting, people, finance, legal, it, operations, science, production.
`includeTotal`	No	Also return pagination.total, the number of records matching these filters across all pages. Costs no credits.
`technologies`	No	Technologies named in the roles, e.g. snowflake, salesforce, kubernetes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedOct 14, 2026

removedInput schema / properties / fundedWithinDays

Removed value: -{
-  "description": "Only companies that announced a funding round this many days before the signal.",
-  "maximum": 365,
-  "minimum": 1,
-  "type": "integer"
-}

Changed4 schema fields changedOct 14, 2026

changedInput schema / properties / eventType / description

Previous value: -"Signal types. Canonical values: leadership_opening, team_buildout, hiring_surge, hiring_freeze, location_expansion, hard_to_fill, leadership_filled."New value: +"Signal types. Canonical values: leadership_opening, founding_role, role_family_scaling, technology_hiring, team_buildout, hiring_surge, hiring_freeze, location_expansion, hard_to_fill, leadership_filled."

changedInput schema / properties / eventType / items / enum

Previous value: -[
-  "leadership_opening",
-  "team_buildout",
-  "hiring_surge",
-  "hiring_freeze",
-  "location_expansion",
-  "hard_to_fill",
-  "leadership_filled"
-]New value: +[
+  "leadership_opening",
+  "founding_role",
+  "role_family_scaling",
+  "technology_hiring",
+  "team_buildout",
+  "hiring_surge",
+  "hiring_freeze",
+  "location_expansion",
+  "hard_to_fill",
+  "leadership_filled"
+]

addedInput schema / properties / fundedWithinDays

Added value: +{
+  "description": "Only companies that announced a funding round this many days before the signal.",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / roleFamily

Added value: +{
+  "description": "Role families, e.g. sales_development, revops, security. Canonical values: sales_development, sales, sales_engineering, revops, gtm_engineering, partnerships, marketing, demand_gen, product_marketing, content_brand, customer_success, support, software_engineering, hardware_engineering, infrastructure, security, data_engineering, data_analytics, ml_ai, product_management, design, recruiting, people, finance, legal, it, operations, science, production.",
+  "items": {
+    "enum": [
+      "sales_development",
+      "sales",
+      "sales_engineering",
+      "revops",
+      "gtm_engineering",
+      "partnerships",
+      "marketing",
+      "demand_gen",
+      "product_marketing",
+      "content_brand",
+      "customer_success",
+      "support",
+      "software_engineering",
+      "hardware_engineering",
+      "infrastructure",
+      "security",
+      "data_engineering",
+      "data_analytics",
+      "ml_ai",
+      "product_management",
+      "design",
+      "recruiting",
+      "people",
+      "finance",
+      "legal",
+      "it",
+      "operations",
+      "science",
+      "production"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

AddedOct 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already mark it read-only, non-destructive and open-world, so the description need not restate safety. It adds meaningful behavior beyond the schema: results are newest-first, each signal includes the underlying roles, and every returned signal costs one credit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, with purpose and signal categories front-loaded, followed by filters and the cost note. There is no filler.

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 read-only, 14-parameter listing tool with no output schema, the description covers purpose, filter dimensions, ordering and credit cost. It is adequate, though it could say more about the shape of a signal or pagination behavior.

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%, so the 14 parameters are already documented in the schema. The description groups them as type, function, seniority, company and time window, but adds no syntax, defaults, or operator detail beyond that.

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 uses the specific verb 'List' and names the resource 'hiring signals', then scopes them to companies' own job boards and newest-first ordering. It enumerates the signal categories, so an agent knows what it returns, though it does not explicitly differentiate from siblings like company_hiring.

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 says the result can be filtered by type, function, seniority, company or time window, which implies the tool is for targeted signal searches. But it never states when to choose this over company_hiring or other sibling tools, nor any when-not conditions.

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

All signals 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.

Resources

Need Help?