Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

datasets_jobs_companies

Search for companies that are hiring. Filter by board status, ATS provider, and minimum open roles.

Instructions

Find which companies are hiring. Searches the discovered company board registry — which companies are hiring, on which ATS, with how many open roles. status enum: active, empty, gone, blocked, pending. sort enum: open_desc, company_asc, crawled_desc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoMatch on company name / domain
pageNoPage number, default 1
sortNoSort enum: open_desc, company_asc, crawled_desc
statusNoBoard status. Enum: active, empty, gone, blocked, pending
providerNoATS provider filter
page_sizeNoPage size, default 20, max 100
min_open_rolesNoMinimum open roles
Behavior3/5

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

With no annotations, the description carries the burden. It describes a read-like search but does not explicitly state non-destructive behavior or mention any side effects. It covers the functional behavior adequately but is not fully transparent.

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 description is two sentences, concise and front-loaded with the primary purpose. However, the second sentence is a bit run-on and could be better structured (e.g., bullet points for enums).

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

Completeness3/5

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

The description lacks output structure info and default behavior when no parameters are provided. With 7 optional parameters, this gap reduces completeness slightly. Still adequate for a simple listing tool.

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 parameter descriptions. The description redundantly lists enum values already in the schema, adding no new meaning. Baseline score applies as description does not enhance parameter understanding beyond the schema.

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

Purpose4/5

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

The description clearly states it finds hiring companies and searches a company board registry, listing ATS and open role counts. However, it does not differentiate itself from sibling tools like datasets_jobs_company_item or datasets_jobs_search, which could overlap.

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?

No guidance is provided on when to use this tool versus alternatives such as datasets_jobs_search or jobs_company_search. The description lacks context about its specific role among the many job-related siblings.

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

Install Server

Other Tools

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/Crawlora-org/crawlora-mcp'

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