Skip to main content
Glama
鱼泡求职 MCP

鱼泡求职 MCP

by Ahellowyy

yupao_list_saved_jobs

Read-only

Read locally saved candidate jobs by tag and status without contacting the platform, letting you filter your candidate pool by specific criteria.

Instructions

按标签、状态读取本机候选池,不请求平台。

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

Input Schema

NameRequiredDescriptionDefault
tagNo
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are known. The description reinforces this with '不请求平台', which is consistent and mildly useful, but it omits any behavioral detail such as whether an empty result means no saved jobs, how limit truncates, or whether the data can be stale relative to the platform.

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?

A single compact sentence with no filler, and the filter information is front-loaded before the locality note. It is efficient, though the terseness comes partly from omitted information rather than discipline.

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

Completeness2/5

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

With three undocumented parameters, no output schema, and no enum constraints, an agent cannot know what valid tag/status strings are or what limit does. The description does not fill that gap.

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

Parameters2/5

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

Schema description coverage is 0%, so all three parameters must be explained here. The description covers tag and status only at the level of naming them, and says nothing about the limit parameter (default 100) or accepted tag/status values (no enums in schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (本机候选池, the local candidate pool) and two filters (tag, status), and the 'does not request platform' clause signals it is a local read. However, it never says this returns *saved jobs*, so the relationship to the tool name and to the sibling yupao_list_matches remains ambiguous.

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

Usage Guidelines2/5

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

There is no indication of when to pick this over yupao_list_matches or yupao_search_jobs, nor any prerequisite. The only usage-adjacent signal is that it works offline against the local pool.

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