Market and Regulatory Data Feeds — Zinin M2M Hub

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

Name	Required	Description
`max_items`	No	How 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_days`	No	Skip 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_filter`	No	Optional 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_url`	No	Advanced: override the boss.az sitemap URL this Actor walks. Leave empty to use the live boss.az sitemap. Mainly useful for diagnostics.
`fetch_full_description`	No	Include 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.4/5.0

Behavior4/5

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

Annotations already indicate read-only and non-destructive behavior. The description adds useful context about how the tool operates (walks sitemap, visits each detail page) and pricing. Parameter descriptions further reveal behaviors like compensating for closed jobs and lack of server-side keyword search, going beyond the existing annotations.

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 main description is two concise sentences, effectively summarizing the tool's purpose, source, and output. Parameter descriptions are detailed but purposeful, with no filler. The pricing note is brief and useful. Overall, tightly structured and front-loaded.

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?

Despite having no output schema, the description specifies the row fields (title, company, location, posted date, link) and explains the data acquisition method. With 5 parameters thoroughly described and no required params, the tool is fully self-contained and complete for an agent to use correctly.

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?

Schema coverage is 100%, but the description enriches each parameter with practical semantics: max_items explains target vs. guarantee, freshness_days explains the 'bump' behavior, keyword_filter clarifies client-side filtering, and fetch_full_description notes no extra request cost. This adds significant 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 clearly states the tool's function: fetching job postings from Azerbaijan's boss.az. It specifies the data source (sitemap and structured job markup) and output fields (title, company, location, posted date, link), distinguishing it from other job-related siblings by region and site.

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

Usage Guidelines3/5

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

The description implies usage for accessing boss.az job postings but does not provide explicit guidance on when to use this tool versus alternative job listing tools (e.g., jobs-ch-swiss, xing-jobs). No exclusions or alternative recommendations are mentioned.

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

All Market and Regulatory Data Feeds — Zinin M2M Hub tools Inspect

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

Disambiguation2/5

Many tools have overlapping purposes, with over a dozen real-estate scrapers and half a dozen job boards differentiated only by geography. While descriptions are clear, an agent would struggle to pick the correct tool without prior knowledge of the specific site or region, leading to frequent misselection.

Naming Consistency2/5

Tool names use a mix of lowercase-hyphenated (boss-az, clinical-trials-monitor), underscore (pricing_info), and long descriptive phrases (official-gazette-regulatory-action-router). No consistent verb_noun pattern exists; some start with source domains, others with action nouns. This lack of predictability makes navigation confusing.

Tool Count3/5

36 tools is on the heavy side for a server that could have been more focused. While a 'data hub' can justify many endpoints, the high number of near-identical scrapers (12+ real estate, 6+ job boards) suggests bloat rather than well-scoped functionality. A leaner set with parameterized regional filters would be more appropriate.

Completeness2/5

The claimed domain 'Market and Regulatory Data Feeds' is poorly served: there are no stock/forex/commodity price feeds, few global regulatory sources (only FDA, SEC, EU tenders), and many tools are for job and property listings which are tangential. The set feels like a random aggregation rather than a coherent surface, with obvious gaps for core market and regulatory data.

Resources

Need Help?