Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

greenhouse_ecommerce_retail_hiring_enricher

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. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  2. First observed

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about what data is returned, whether calls cost quota, rate limits, freshness, or pagination. 'Real-time' and 'extraction feed' are the only behavioral crumbs and they are too vague to act on.

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 every word is wasted — the sentence loops the tool title back on itself rather than front-loading useful information. Brevity here reflects missing content, not efficiency.

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?

A scraping/extraction tool with no annotations and no output schema needs the description to say what fields or signals come back and in what shape. None of that is present, leaving the agent unable to predict results or judge relevance against siblings.

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 a single self-documented 'maxResults' parameter (default 10), so the schema already explains the only input. The description adds no meaning beyond it, which is the baseline case when the schema does the work.

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 circular: 'Greenhouse E-Commerce & MarTech Hiring Signal Scraper' is restated as a 'feed for Greenhouse E-Commerce & MarTech Hiring Signal Scraper.' Only the phrase 'real-time structured data extraction' hints at the actual operation, 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 Guidelines1/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 like greenhouse_b2b_tech_hiring_velocity_scraper or greenhouse_ai_ml_engineering_jobs_radar. The agent must guess purely from the tool name.

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.