Skip to main content
Glama
鱼泡求职 MCP

鱼泡求职 MCP

by Ahellowyy

yupao_search_jobs

Read-only

Search Yupao job listings by keywords and city, returning paginated structured results. Use it to find matching roles without applying or messaging.

Instructions

按关键词与城市实时搜索鱼泡岗位,分页返回结构化结果。不会投递或打招呼。

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": {
      "keywords": "<keywords>"
    },
    "name": "yupao_search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo上海
pageNo
keywordsYes
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context by stating it searches in real time, returns paginated structured results, and will not apply or greet, which reinforces the safe read-only nature of the tool.

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?

The description is two short sentences with no wasted language. The core purpose and the non-action constraint are front-loaded and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the basic search behavior and explicitly rules out application/greeting side effects. For a search tool with four parameters, no schema descriptions, and no output schema, it could do more to explain pagination behavior, defaults, and result characteristics.

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 0%, so the description must carry parameter meaning. It mentions keyword and city search as well as pagination, which maps conceptually to all four parameters, but it does not explain defaults, page-size limits, or expected formats.

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 verb and resource: real-time job search by keyword and city. It distinguishes itself from action-oriented siblings by explicitly saying it will not apply or greet, though it does not explicitly separate itself from detail or saved-job tools.

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 implies the tool is for searching jobs and clarifies that it performs no application or greeting actions. However, it does not explicitly state when to use this instead of alternatives such as getting job details or listing saved jobs.

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