Skip to main content
Glama

Microburbs Australian Property Data

Australia · Job advertisements over time

australia_economy_job_vacancies
Read-onlyIdempotent

Monthly count of online job advertisements for Australia and each state and territory since January 2006, by occupation group and by skill level.

Coverage: Australia and all 8 states and territories; monthly, January 2006 to September 2026 (249 months). Current to 2026-09-01. Full description, field list and method: /v1/datasets/job-vacancies.

Price: 5¢ per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "australia_economy_job_vacancies"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
fieldsNoComma-separated subset of: total_ads, managers, professionals, technicians_trades, community_personal_service, clerical_admin, sales, machinery_drivers, labourers, skill_level_1, skill_level_2, skill_level_3, skill_level_4, skill_level_5. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description goes beyond them in a genuinely useful way by disclosing the per-call price (5¢), the exact coverage window (Jan 2006 – Sep 2026, 249 months), and the data currency date — all things an agent needs to decide whether to call.

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 tight blocks: what the data is, coverage window, and a pointer to deeper docs, with the price called out separately. Nothing is redundant, though the coverage paragraph repeats the January 2006 / 2026 dates already implied in the opening sentence.

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 read-only timeseries endpoint with a fully documented three-parameter schema and no output schema, the description supplies granularity, geographic scope, temporal coverage, data currency, cost, and a link to field-level documentation. Only the return shape itself is left undocumented, which is acceptable given the datasets pointer.

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 `from`, `to` and `fields` are already fully documented including the accepted date formats and the field-name list. The description only restates the available breakdowns (occupation group, skill level) and the start period, adding marginal meaning beyond the schema — baseline 3 applies.

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?

Opens with a specific verb+resource+grain: monthly count of online job advertisements for Australia and each state/territory, broken down by occupation group and skill level. The scope is unambiguous, though it does not explicitly distinguish itself from the state-focused sibling (states_economy_job_vacancies) — the phrase 'Australia and each state and territory' could describe either.

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?

No explicit when-to-use / when-not guidance and no alternative tool is named. The pointer to `/v1/datasets/job-vacancies` for the full description, field list and method implies where to get more context, and the stated coverage makes the fit inferable, but routing between this and the state-level sibling is left to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources