Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_remote_hiring_signals

Read-onlyIdempotent

Find deduplicated B2B companies hiring remote cross-border talent across LATAM, Europe, EMEA, APAC and more, with verified domains, careers URLs, salary ranges, tech stack and hiring velocity.

Instructions

Find deduplicated B2B companies actively hiring remote, cross-border, LATAM, Europe, EMEA, and APAC talent across 6 live feeds with verified root company domains (domain), careers URLs, disclosed salary ranges, tech stack, and hiring velocity (corridordata/global-remote-hiring-signals).

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": "search_remote_hiring_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNoOptional role, skill, or tech stack keywords (OR logic, e.g. ['python', 'ai', 'devops']).
maxItemsNoMaximum number of deduplicated hiring company leads to return.
minOpenRolesNoMinimum active remote job openings at the same company.
targetRegionsNoFilter companies hiring in specific remote regions.
withSalaryOnlyNoOnly return companies with disclosed salary ranges.
crossBorderOnlyNoExclude single-country domestic remote roles (e.g. 'US Only') to isolate cross-border / EOR hiring signals.
postedWithinDaysNoOnly include fresh postings published within the last N days.
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, so the bar is lower. The description still adds real value: it discloses provenance ('across 6 live feeds'), deduplication semantics, and that domains are 'verified root company domains'. It does not mention rate limits or how billing is triggered per returned lead.

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

Conciseness3/5

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

It is a single long run-on sentence, though the core purpose is front-loaded before the field enumeration. The region list ('LATAM, Europe, EMEA, and APAC') duplicates the schema enum and the parenthetical feed identifier is low-value for tool selection. Tightening would improve it without losing information.

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?

With no output schema, the description usefully enumerates the returned fields (domain, careers URLs, salary ranges, tech stack, hiring velocity), which is the main gap it needed to fill. Annotations handle the safety profile and the schema handles parameters fully. Missing only result volume/pagination expectations and cost 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 coverage is 100% with eight fully documented parameters, so the baseline is 3. The description echoes the region and salary concepts but adds no syntax, defaults, or interaction rules beyond the schema. The phrase 'cross-border / EOR hiring signals' gives some interpretive context for crossBorderOnly but nothing that the schema does not already state.

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 states a specific verb ('Find') and a precise resource ('deduplicated B2B companies actively hiring remote... talent'), plus the enrichment fields returned (domain, careers URLs, salary ranges, tech stack, hiring velocity). It implicitly separates itself from job-posting siblings by emphasizing company-level deduplicated leads with verified root domains. It stops short of naming which sibling to use for role-level or single-region searches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite siblings like search_multi_ats_jobs and search_apac_jobs that plausibly overlap. The agent must infer from the described output shape that this tool yields company leads rather than individual postings. Nothing warns about the pay-per-event cost model beyond the schema's maxTotalChargeUsd parameter.

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