Skip to main content
Glama
mambalabsdev

Workplace Program Detector MCP Server

by mambalabsdev
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Workplace Program Detector MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

MCP server for the Mamba Labs Workplace Program Detector actor on Apify.

A company domain in, the people programs that company publishes out: employee resource groups, DEI, wellbeing and mental health, learning and tuition support, parental and caregiver leave, and volunteering.

Install

npx -y @mambalabsdev/mcp-workplace-program-detector

Claude Desktop

{
  "mcpServers": {
    "mamba-workplace-program-detector": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-workplace-program-detector"],
      "env": { "APIFY_TOKEN": "your-apify-token" }
    }
  }
}

Get an Apify token at console.apify.com/account/integrations.

Related MCP server: Networking MCP

Tool

detect_workplace_programs

A company domain in, the people programs that company publishes out: employee resource groups, DEI, wellbeing and mental health, learning and tuition support, parental and caregiver leave, and volunteering.

Input

Type

Required

Notes

domain

string

yes

Bare domain, for example hubspot.com. Protocol and path are stripped.

ats_slug

string

no

Skip ATS discovery and read this Greenhouse, Lever or Ashby board slug directly.

programs

array

no

Report only these families: erg, dei, wellbeing, learning, parental, volunteering. Omit for all six. A family you do not select reports null, never false, and is not counted in program_count.

scan_job_postings

boolean

no

Reads the company's live job bodies from its ATS. This path finds benefits language that marketing pages omit.

scan_web_pages

boolean

no

Probes the careers, culture, benefits, DEI and ESG paths. This path finds ERG and volunteering language that job postings omit.

max_pages

string

no

Sent as a string for Clay. Clamped to 1 to 25.

skipCache

enum

no

false uses the 14 day cache, true forces a fresh crawl. Sent as a string for Clay, matching the fleet convention.

Billing

You are charged per domain analyzed, plus a small actor start fee.

Pricing is on the actor's Apify page. Running this server consumes Apify credits.

What this server does and does not do

It is a thin client for the Apify actor. It passes your input through and returns the actor's output unchanged. Every behavior described above lives in the actor, not here.

Errors are surfaced, never swallowed. An invalid input, an invalid token, an exhausted balance, a timeout, or a run that returns anything other than a dataset all come back as an explicit tool error rather than as an empty result.

Source

The actor is on the Apify Store. This wrapper is MIT licensed.

Built by Mamba Labs

Available Tools

1 tool
detect_workplace_programsDetect Workplace ProgramsA
Read-onlyIdempotent

Detect which people programs a company publishes on its own surfaces, and return one flat row per domain. It reads two independent paths and each catches what the other misses: the company's live job postings through its Greenhouse, Lever or Ashby board, which is where benefits language that marketing pages omit shows up, and the careers, culture, benefits, DEI and ESG pages on the website, which is where employee resource group and volunteering language shows up. Either path can be turned off. If you already know the company's ATS board slug, pass ats_slug to skip discovery and read that board directly. Results are cached for 14 days and skipCache forces a fresh crawl. This reports what a company publishes, which is not the same as what it does: absence of a signal means the company does not say it publicly, not that the program does not exist. Requires an APIFY_TOKEN and consumes Apify credits. Read only: it reads public pages, it writes nothing.

ParametersJSON Schema
NameRequiredDescriptionDefault
domainYesBare domain, for example hubspot.com. Protocol and path are stripped.
ats_slugNoSkip ATS discovery and read this Greenhouse, Lever or Ashby board slug directly.
max_pagesNoSent as a string for Clay. Clamped to 1 to 25. Default: "14".
skipCacheNofalse uses the 14 day cache, true forces a fresh crawl. Sent as a string for Clay, matching the fleet convention. Default: "false".
scan_web_pagesNoProbes the careers, culture, benefits, DEI and ESG paths. This path finds ERG and volunteering language that job postings omit. Default: true.
scan_job_postingsNoReads the company's live job bodies from its ATS. This path finds benefits language that marketing pages omit. Default: true.

TDQS

A4.8/5.0
Behavior5/5

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

The description adds extensive behavioral context beyond the annotations: it reads two independent paths, caches results for 14 days, requires an APIFY_TOKEN, consumes credits, and clarifies that absence of a signal does not mean the program doesn't exist. This is highly transparent and aligns with the readOnlyHint, idempotentHint, and openWorldHint.

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?

The description is detailed yet efficient, with each sentence contributing necessary context: purpose, two data paths, parameter usage, caching, and interpretation of results. It is front-loaded with the core purpose and organized logically.

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

Completeness5/5

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

Even without an output schema, the description explains the return shape (one flat row per domain), covers all six parameters implicitly, and discloses operational requirements (APIFY_TOKEN, credits) and limitations. This makes it fully self-contained for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema covers all parameters, the description enriches several: it explains why ats_slug skips discovery, what skipCache does, and how scan_web_pages and scan_job_postings offer complementary signal paths. This adds practical meaning beyond the schema field descriptions.

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

Purpose5/5

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

The description clearly states what the tool does: detects which people programs a company publishes on its own surfaces, returning one flat row per domain. It specifies the exact resources (job postings via ATS, website pages) and distinguishes this from merely reporting on actual programs, making the purpose unambiguous even without siblings.

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

Usage Guidelines4/5

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

The description provides clear context on when to use the tool and its sub-paths (e.g., turning off either scan path, using ats_slug to skip discovery). It doesn't explicitly mention alternative tools or when not to use it, but given the absence of siblings, this is sufficient.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observeddetect_workplace_programs
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.7/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap. The tool's purpose is clear and distinct.

Naming Consistency5/5

With a single tool, naming is trivially consistent. The verb_noun pattern (detect_workplace_programs) is clear and descriptive.

Tool Count3/5

The server has only one tool, which is borderline for a typical MCP server. However, the narrow, focused purpose of detecting workplace programs justifies a single, comprehensive tool.

Completeness5/5

The tool thoroughly covers the domain of detecting publicly published workplace programs by reading both job postings and website pages. It includes options to skip discovery, force refresh, and explains limitations, providing a complete read-only workflow.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Networking MCP

    otnielba
    A
    license
    Not graded
    quality
    B
    maintenance
    Local-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.
    MIT

  • AI-Agentic-MCP

    FiddelMyStick
    F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server exposing employee info retrieval and web search tools, designed to be consumed by a LangChain agent for decoupled tool execution.
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mambalabsdev/mcp-workplace-program-detector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server