Skip to main content
Glama

Search remote and hybrid jobs

search_jobs
Read-onlyIdempotent

Search live remote and hybrid job postings on Aworkado, collected daily from employers' own career pages. Returns up to 10 of the newest matching postings with their Aworkado links, and the total number of matches. All filters are optional and combine with AND.

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_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoSeniority: Entry, Mid-level or Senior.
queryNoKeywords matched against the job title and the company name, e.g. "python backend" or "Stripe".
regionNoA region instead of single countries: europe, latin-america, asia, africa, middle-east, north-america, oceania, or anywhere (postings open worldwide).
countriesNoISO 3166-1 alpha-2 codes of the countries the candidate can work from, e.g. ["IN", "PH"]. A posting matches when it is open to any of them.
workplaceNoremote or hybrid. Leave out for both.
jobFunctionNoOne job function, exactly as listed: Software Engineering, Data & Analytics, DevOps & Cloud, QA & Testing, IT & Security, Hardware Engineering, Product Management, Project Management, Design, Marketing, Sales, Business Development, Account Management, Customer Support, Operations, Finance & Accounting, HR & Recruiting, Legal & Compliance, Writing & Content, Education & Training, Healthcare, Research, Consulting, Administrative, Other.
postedWithinNoOnly postings published within the last day, week or month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 description's added value is in disclosure of result shape and scope: max 10 newest matches, Aworkado links, and a total match count. This is valuable because there is no output schema; only minor gaps remain, such as whether more than 10 results can ever be retrieved.

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?

Two sentences with no filler: the first establishes what is searched and the data source, the second states the return shape and filter combination rule. Information is front-loaded and nothing is repeated from the schema.

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?

With 7 all-optional params at full schema coverage and no output schema, the description covers what the tool searches, result cap, and returned fields, which is enough to call it correctly. It falls short only on edge behaviors such as result truncation limits and result ordering ties.

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 100%, so the schema already explains each of the 7 optional filters in detail. The description adds only the AND-combination semantics across filters, which is a real but modest supplement, so the baseline of 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?

States a specific verb and resource ('Search live remote and hybrid job postings on Aworkado') plus provenance ('collected daily from employers' own career pages'). It is clearly a search/list operation, which implicitly separates it from the get_job sibling, but it never names that sibling or states the distinction explicitly.

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?

Adds one genuinely useful usage rule: 'All filters are optional and combine with AND,' which tells the agent how to compose calls. It gives no explicit when-to-use vs. when-to-call-get_job guidance and does not explain behavior when zero filters are supplied (i.e., whether it browses all postings).

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.