SylvaraJob

Buscar ofertas de empleo

buscar_ofertas

Read-onlyIdempotent

Busca ofertas de empleo activas. Devuelve primero las ofertas PROPIAS publicadas por empresas en SylvaraJob (España; ficha completa y URL pública en sylvarajob.com/empleo) y después las EXTERNAS, publicadas por otras empresas en sus propias webs mediante Greenhouse, Lever, Ashby o Teamtailor (solo título, empresa, ciudad, fecha y enlace a la fuente). La búsqueda por texto amplía cada palabra con sinónimos de profesiones y sectores en 8 idiomas (programador ↔ developer ↔ sviluppatore ↔ 程序员; camarero ↔ waiter; mozo de almacén ↔ warehouse operative) e ignora mayúsculas, acentos, plurales y género. Envía en «terminos» el término tal como lo dijo la persona MÁS su traducción al inglés (p. ej. ["enfermera", "nurse"]). Al filtrar por provincia o ciudad van primero las ofertas de esa zona y después las remotas del mismo país (coincide_zona=false). Filtros opcionales: texto/terminos, provincia, ciudad, país (ISO-2), modalidad y origen. Paginado, máximo 20 por página. Search active job offers with multilingual synonyms: SylvaraJob own postings first (full data, public URL), then external postings (title, company, city, date and source link only). Pass the user's term plus its English translation in «terminos».

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pais`	No	País en ISO 3166-1 alfa-2 (ES, PT, FR, DE, US…). Sin filtro se devuelven todos.
`texto`	No	Palabras del título, la empresa o la descripción (p. ej. «camarero», «contable», «Datadog»). Cada palabra se amplía con sus sinónimos en 8 idiomas.
`ciudad`	No	Municipio o ciudad (p. ej. «Barcelona», «Getafe»). Sin filtro de modalidad, detrás de la zona se listan las ofertas remotas del mismo país.
`idioma`	No	Idioma del texto del resumen (los datos de las ofertas van en el idioma en que se publicaron).	es
`origen`	No	Qué fuentes incluir.	todas
`pagina`	No
`terminos`	No	Términos alternativos (basta que coincida uno): el término de la persona y su traducción al inglés (p. ej. ["camarero", "waiter"], ["infermiera", "nurse"]). Cada uno se amplía con sinónimos. Se puede combinar con «texto».
`modalidad`	No
`provincia`	No	Provincia de la oferta propia (p. ej. «Lleida», «Madrid»); en externas se compara con ciudad o región. Sin filtro de modalidad, detrás de la zona se listan las ofertas remotas del mismo país.
`por_pagina`	No

Output Schema

TableJSON Schema

Name	Required	Description
`pagina`	Yes
`ofertas`	Yes
`busqueda`	No	Cómo se interpretó la búsqueda
`por_pagina`	Yes
`total_paginas`	Yes
`total_propias`	Yes
`total_externas`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare the safe read profile (readOnly, idempotent, non-destructive), and the description adds substantial behavior beyond them: two-tier result ordering with differing field richness per source, multilingual synonym expansion across 8 languages, normalization of case/accents/plurals/gender, and zone-then-remote ordering. This is exactly the extra context an agent needs.

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 with purpose and the key dual-source behavior, and the dense Spanish paragraph earns most of its length. The trailing English restatement is a condensed duplicate that adds accessibility but also redundancy.

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?

For a 10-parameter, zero-required search tool with an output schema, the description covers the non-obvious essentials: result composition, synonym behavior, term-handling instruction, and location-based ordering. Return-value detail is appropriately left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 70% and the description adds real meaning beyond it: how «terminos» should be filled (user term + English translation), how «texto» expands into cross-language synonyms, and how provincia/ciudad trigger zone-first ordering. Pagination and enum parameters are left to the schema, which already documents them.

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?

It states a specific verb and resource ('Busca ofertas de empleo activas') and precisely characterizes the two result sets (own vs. external postings). It never names the sibling tools (ver_oferta, listar_categorias_y_provincias), so differentiation from them is inferable but not explicit.

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

Usage Guidelines4/5

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

Gives clear operational context: how to populate «terminos» with the user's term plus its English translation, how province/city filters order results, and that all filters are optional. It lacks an explicit 'use this instead of X' exclusion, but the usage conditions are well conveyed.

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

All SylvaraJob tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?