Skip to main content
Glama

Microburbs Australian Property Data

State · Job advertisements over time

states_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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>"
    },
    "name": "states_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.
stateYesState or territory abbreviation: nsw, vic, qld, sa, wa, tas, act or nt.
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.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered without the text. The description does add genuinely useful non-schema facts: the coverage window, the currency date (2026-09-01), and a per-call price of 5¢. It says nothing about response shaping, pagination, or what happens when a range exceeds the coverage window.

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?

Front-loaded topic sentence, then a compact coverage line, then price — every element is scannable and earns its place. Mild redundancy between the title and the opening clause, but no filler.

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?

No output schema exists, so the description must carry the return shape, and the phrase 'monthly count ... by occupation group and by skill level' does imply the measure and dimensions, supplemented by the field pointer URL. Missing is any statement of how the national aggregate relates to the per-state `state` parameter, which matters given the required parameter.

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%, with `from`/`to` formats, the state abbreviation list, and the full `fields` vocabulary all documented inline, so the baseline of 3 applies. The description's mention of occupation group and skill level lightly reinforces the `fields` options but adds no format or defaulting detail 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 names a specific metric (monthly count of online job advertisements), the geography (Australia and each state/territory), the granularity (by occupation group and skill level), and the time span since January 2006. It does not, however, distinguish itself from the similarly named sibling australia_economy_job_vacancies, leaving the agent to guess whether this tool also covers the national aggregate.

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?

Use is only implied: the required `state` parameter and the stated coverage make clear this is the state-breakdown tool, and the pointer to `/v1/datasets/job-vacancies` offers a fallback for detail. There is no explicit when-to-use/when-not statement, and no named alternative for national-only queries.

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