Skip to main content
Glama
GMPSignal Real-Time Intelligence MCP (59 Tools)

GMPSignal Real-Time Intelligence MCP (59 Tools)

Official
by xpayrcom

greenhouse_ecommerce_retail_hiring_enricher

Extract structured Greenhouse e-commerce and MarTech hiring signals in real time to identify companies actively expanding retail and marketing teams for timely B2B outreach.

Instructions

Greenhouse E-Commerce & MarTech Hiring Signal Scraper: Real-time structured data extraction feed for Greenhouse E-Commerce & MarTech Hiring Signal Scraper.

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_ecommerce_retail_hiring_enricher"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about data source, freshness guarantees behind 'real-time', rate limits, pagination, or result shape. 'Real-time structured data extraction feed' is the only behavioral claim and it is unverifiable marketing phrasing rather than actionable context.

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

Conciseness2/5

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

It is short, but the length comes from verbatim repetition of the tool name rather than information. Nothing is front-loaded beyond the title, and the one substantive clause is buried in a restatement.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place an agent could learn what fields are returned (job titles, companies, counts, dates?) and what 'hiring signal' means. It supplies none of that, leaving the agent unable to judge whether the output fits its task.

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?

The single parameter (maxResults) has 100% schema description coverage, so the baseline of 3 applies. The description adds no meaning beyond the schema — it does not explain what a 'structured item' is or how maxResults interacts with the feed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a tautology: it restates the tool name twice ('Greenhouse E-Commerce & MarTech Hiring Signal Scraper ... feed for Greenhouse E-Commerce & MarTech Hiring Signal Scraper') without ever saying in plain terms what the tool returns. Only the words 'scraper' and 'structured data extraction' hint at a verb+resource, and nothing distinguishes it from the many sibling greenhouse_* hiring scrapers.

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 exclusion criteria, and no mention of how this differs from siblings such as greenhouse_b2b_tech_hiring_velocity_scraper or greenhouse_ai_ml_engineering_jobs_radar. At best the name implies a sector focus (e-commerce/MarTech hiring), which is weak implied usage rather than stated guidance.

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

Deploy Server

Other Tools