Skip to main content
Glama

Market Data

by com.timzinin.api

Boss.az Jobs

boss-az
Read-only

Job postings from Azerbaijan's boss.az, taken through the site's own sitemap and the structured job markup on each detail page. One row per posting: title, company, location, posted date, link. — $0.02/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_itemsNoHow many job rows to deliver, at most. This Actor walks boss.az's own job sitemap and visits each candidate job page individually — some listed jobs turn out already closed by the time they're visited, which is normal, not a fault. Extra candidates are attempted automatically to compensate, so this number is a target, not a guarantee.
freshness_daysNoSkip sitemap entries not updated within this many days. boss.az's own sitemap 'last modified' date also moves when an employer renews ("bumps") an old posting, so this is a rough recency filter, not an exact posting-age filter.
keyword_filterNoOptional case-insensitive substring match against each job's title, applied on this Actor's side after fetching the job's own page. boss.az's job search itself needs a browser session and is not used here — there is no server-side keyword search on this Actor. Leave empty to keep every job found.
sitemap_override_urlNoAdvanced: override the boss.az sitemap URL this Actor walks. Leave empty to use the live boss.az sitemap. Mainly useful for diagnostics.
fetch_full_descriptionNoInclude the job's full description text in the output row. This Actor already fetches each job's own page to get any data at all (title, company, location...), so the description costs no extra request either way — this setting only controls whether it's kept in the row.

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish the tool as read-only and non-destructive. The description adds the method (sitemap walking and detail page scraping) but does not disclose important behavioral quirks like closed jobs or that max_items is a target, not a guarantee—those details are confined to parameter descriptions.

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 exceptionally concise: two sentences that state the source, method, output shape, and pricing, with no filler or redundant information. It is front-loaded and every word adds 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?

For a simple read-only job scraper with a rich schema and strong annotations, the description covers the essential context: source, method, output, and cost. However, it omits usage boundaries and the non-guaranteed item count in the main text, relying on the schema for those nuances.

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 description coverage is 100%, so the baseline is 3. The main description does not add parameter-level semantics, but each parameter already has a rich, detailed description in the input schema, covering behavior like 'target, not a guarantee' and rough recency filtering.

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 the tool's function: it returns job postings from Azerbaijan's boss.az via sitemap and structured markup, and specifies the output fields ('One row per posting: title, company, location, posted date, link'). This distinguishes it from sibling job tools by naming the exact site and region.

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 use case is clear—this tool is for retrieving boss.az job listings—but it does not explicitly mention when not to use it or offer alternative tools for other regions or job boards. There are no exclusions, but the context is sufficiently clear for an agent to select it appropriately.

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

All Market Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources