Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jobs_gem_board

Fetch a company's public Gem job board postings, including full HTML descriptions and compensation ranges. Pass the company's Gem vanity URL slug to get clean JSON.

Instructions

List a company's Gem job board. Lists a company's public Gem (gem.com) board postings with inline detail (full HTML description, and compensation when the company publishes a pay range). The company is the Gem vanity URL slug from its careers URL.

Input Schema

NameRequiredDescriptionDefault
companyYesGem vanity URL slug (careers URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses what each posting includes (full HTML description, compensation only when the company publishes a pay range), which is real value. It omits pagination, result limits, and auth/rate-limit behavior expected of a list endpoint.

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?

Three compact sentences, front-loaded with the action and enriched with return-content detail. There is mild redundancy between the first two sentences, which both restate that it lists a company's Gem board.

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?

For a single-parameter list tool with no output schema or annotations, the description covers the essentials: what is listed, the meaning of the parameter, and what the postings contain. The only meaningful gap is pagination/volume behavior.

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 baseline is 3. The description's note that "company" is the Gem vanity URL slug from the careers URL essentially restates the schema's own description ("Gem vanity URL slug (careers URL)"), adding no syntax or format detail beyond it.

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 ("List") and resource ("a company's Gem job board") and names the platform (gem.com) explicitly, which cleanly separates it from the many sibling ATS-board tools like jobs_greenhouse_board or jobs_workday_board. It also specifies scope (public postings) and content (inline HTML description, compensation).

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?

It gives clear context for use (fetch a company's public Gem board postings) and tells the agent what the required input represents ("the Gem vanity URL slug from its careers URL"). However, it never names an alternative or a when-not condition, so the agent must infer routing among the sibling board tools.

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