Skip to main content
Glama

Search graduate jobs

search_graduate_jobs
Read-onlyIdempotent

Search covers the website’s latest at most 200 published, valid, open graduate jobs. Counts refer to this window, not the whole database. Filter by city, position type, accepted visa and qualification. Applications remain on the website. This public endpoint returns English natural-language text, preserving sources, conditions and pagination.

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": "search_graduate_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoExact city code from results, e.g. melbourne, sydney or gold_coast.
pageNo
keywordNoCase-insensitive substring of title, company name or qualification name, as on the website.
pageSizeNo
acceptedVisaNoJobs accepting this visa or any visa.
hiringStatusNoOnly open jobs are available in the website list.
positionTypeNoExact published position type.
qualificationNoSubstring of a published qualification name or exact qualification level.

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?

Beyond the readOnly/idempotent/openWorld annotations, the description discloses a real behavioral constraint: a 200-job result window that counts are computed against rather than the whole database, plus only open and valid jobs appearing. It also discloses the return shape loosely (English natural-language text preserving sources, conditions and pagination), though pagination semantics of the window itself are not spelled out.

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?

Four dense sentences with the important constraint (200-job window) front-loaded in sentence one. No filler, though the final sentence about 'English natural-language text' is slightly awkward and could be tighter.

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 an eight-parameter, all-optional search tool with no output schema, the description covers scope, result cap and return nature adequately. Minor gaps remain around how the window interacts with paging and what the response envelope contains, but nothing critical to calling it correctly is missing.

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 75% and the schema already documents city codes, enum values and keyword matching rules. The description only groups four of the eight filters and adds no meaning for keyword, page, pageSize or hiringStatus, so it is essentially baseline.

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?

Specific verb and resource: 'Search ... graduate jobs', with an explicit scope of the latest 200 published, valid, open jobs. It implicitly contrasts with get_graduate_job by being the search/list side, but does not name any sibling to sharpen the distinction.

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 lists the filterable dimensions (city, position type, visa, qualification) and notes that applications stay on the website, which implies a read-only browsing use case. It never states when to prefer this over get_graduate_job or when-not to use it, and the keyword/paging options are left unmentioned.

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