Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

greenhouse_b2b_tech_hiring_velocity_scraper

Read-onlyIdempotent

Greenhouse B2B Tech Hiring Velocity API: Tracks open engineering and GTM roles across high-growth B2B tech companies on Greenhouse ATS.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum job listings to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum job listings to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description adds only source scope (Greenhouse ATS, high-growth B2B tech) and says nothing about freshness of the scrape, rate limits, or whether results are a live snapshot — meaningful for a scraper. The word 'Tracks' also mildly suggests continuous monitoring, which conflicts with a one-shot query tool.

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?

One front-loaded sentence with no padding, and the scope qualifiers are packed efficiently. The 'Greenhouse B2B Tech Hiring Velocity API:' prefix duplicates the annotation title, which is the only wasted token.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description omits what a result actually contains, which matters because 'Hiring Velocity' implies an aggregate metric while the parameter talks about 'job listings to return' — an agent cannot tell whether it gets counts, trend data, or raw postings. For a one-parameter read-only scraper with no output schema, this is the main remaining gap.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains maxResults. The description adds nothing about it — not whether there is an upper cap or how results are ordered when truncating — so it neither helps nor hurts beyond the baseline.

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 names a specific verb and resource: it 'tracks open engineering and GTM roles' at 'high-growth B2B tech companies on Greenhouse ATS', which is enough for an agent to know what data comes back. It doesn't explicitly distinguish itself from siblings like greenhouse_ai_ml_engineering_jobs_radar or greenhouse_fintech_compliance_hiring_tracker, so the sector boundary has to be inferred from the 'B2B tech' framing.

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 when-to-use guidance, no stated preconditions, and no pointer to an alternative tool for adjacent sectors or job boards. An agent must decide on its own whether this or a sibling monitor is the right call.

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.

Resources