Maison de Talents

명품·백화점·면세점 매장 채용공고 검색

search_jobs

Read-onlyIdempotent

[메종 드 탤런트 명품 매장 채용] 한국 백화점·면세점·명품 브랜드 매장 판매직의 진행 중인 채용공고(구인·채용 중인 일자리)를 검색합니다 — 판매직 CA/SA/BA, 뷰티 어드바이저, 매장 매니저, VMD 등. Searches open retail sales jobs and hiring posts at luxury brand boutiques, department stores and duty-free shops in Korea, Seoul and nationwide (e.g. Chanel, Louis Vuitton, Rolex, Lotte Duty Free). 결과 url 은 메종 드 탤런트 공고 상세 페이지이며, 그 페이지에서 원문 공고로 가거나 바로 지원할 수 있습니다. 모든 인자는 선택입니다.

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

Name	Required	Description
`brand`	No	브랜드명 한글/영문 (예: 샤넬, Rolex, 루이비통)
`limit`	No	최대 결과 수(기본 5, 최대 10)
`query`	No	직무·키워드 (예: 판매, 뷰티 어드바이저, 매니저, 면세점)
`region`	No	근무 지역 (예: 서울, 강남구, 부산, 인천공항)

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 19, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuine context beyond that: only currently-open/in-progress postings are returned, results are URLs to 메종 드 탤런트 detail pages from which the original posting or direct application is reachable, and the geographic scope is Korea/Seoul/nationwide.

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?

The description is front-loaded with the core action and scope, and each sentence carries content. It is somewhat longer than necessary because the Korean sentence is effectively restated in English, which adds length without new information.

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 no output schema, the description compensates by explaining that results are detail-page URLs usable for viewing the original posting or applying directly, plus the open-postings-only scope. What is missing is a pointer to get_job for retrieving a single posting's full detail, but for a filtered search tool the essentials are present.

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 all four parameters individually documented, so the baseline is 3. The description mirrors the schema's themes (job categories map to query, brands map to brand) but adds no filtering semantics such as AND/OR behavior across brand+region+query or how matching is performed.

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 gives a concrete verb (검색합니다 / searches) and a precisely bounded resource: open retail sales postings at luxury boutiques, department stores and duty-free shops in Korea, with named job categories (CA/SA/BA, beauty advisor, store manager, VMD) and example brands. It does not explicitly distinguish itself from the sibling get_job, though 'open postings' vs. detail-fetch is reasonably inferable from the URL sentence.

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?

'모든 인자는 선택입니다' usefully tells the agent it can call this with zero filters, and the note that result URLs lead to detail pages where one can apply implies where to go next. However, no sibling is named (get_job for a single posting, get_salary_benchmark for pay data) and there is no explicit when-not guidance.

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

All Maison de Talents 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?