Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_phenom_board

Find jobs on a Phenom People-powered careers site by providing the domain. Searches public listings with keyword, location, category filters and paging.

Instructions

Search a Phenom People tenant's job board. Searches a company's public Phenom People career site (a white-labeled domain such as careers.whataburger.com or jobs.cvshealth.com — Phenom serves the search-results page as server-rendered HTML with the job data embedded inline, not a JSON API, but this is still credential-free public data with no auth, cookie, or session required). domain is the tenant's careers domain from its careers URL. Paged via offset/limit; limit is a best-effort page-size hint some tenants ignore, so count always reflects what actually came back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order, default relevant
limitNoPage size hint, default 10, max 100 (some tenants ignore this and return their own configured page size regardless)
domainYesPhenom tenant careers domain (careers URL)
offsetNoPage offset, default 0
categoryNoFilter: category contains
keywordsNoFree-text keyword search
locationNoFilter: location contains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevant",
+  "recent"
+]
  2. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key traits: server-rendered HTML rather than a JSON API, credential-free access, and limit being a best-effort hint while count reflects actual results. It doesn't describe return shape or error behavior, but covers the main invocation caveats.

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?

The main purpose is front-loaded, followed by a dense but relevant parenthetical about HTML scraping and no-auth access, then paging caveats. It is fairly long, but each sentence contributes operational value.

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?

Despite lacking an output schema, the description provides enough operational context: what domain means, how paging works, how data is sourced, and that no authentication is needed. It doesn't describe the exact return format, though the count caveat partially hints at the response.

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%, so the schema already documents all seven parameters. The description mainly reinforces the domain requirement and limit caveat with examples, adding some context but not substantial semantic value beyond the schema.

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 states a specific verb and resource: searching a Phenom People tenant's job board. It adds concrete examples (careers.whataburger.com, jobs.cvshealth.com) and clarifies this is a public career-site search, distinguishing it from detail-level siblings like jobs_phenom_job.

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?

Provides clear context: use against a company's public Phenom People career site, requiring only the tenant's careers domain, with no auth required. It doesn't explicitly name sibling alternatives or state when not to use this tool (e.g., when a single job detail is needed).

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