Skip to main content
Glama
鱼泡求职 MCP

鱼泡求职 MCP

by Ahellowyy

yupao_get_job_detail

Read-only

Fetches full job details by job_biz_id from search results so AI clients can analyze requirements, responsibilities, and qualifications.

Instructions

根据搜索结果的 job_biz_id 读取完整 JD,供调用方 AI 进行岗位分析。

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": {
      "job_biz_id": "<job_biz_id>"
    },
    "name": "yupao_get_job_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_biz_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the return is a full JD intended for analysis, but says nothing about failure behavior when the ID is invalid or stale, or about payload size.

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?

A single front-loaded sentence with no filler. The precondition and the purpose are both packed into one clause without repetition of the tool name.

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?

For a one-parameter read-only fetch with no output schema, the description covers what is fetched (full JD) and why it exists (job analysis). Only edge-case behavior for a bad job_biz_id is left unaddressed.

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 0%, so the schema carries no semantics for job_biz_id. The description compensates by specifying the parameter's provenance (it comes from search results) and its expected form as an ID string, which is exactly what an agent needs to source it correctly.

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: read the complete JD for a given job_biz_id, plus its intended downstream use (岗位分析). This clearly separates it from yupao_search_jobs, though it does not name that sibling 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?

The phrase '根据搜索结果的 job_biz_id' implies the prerequisite that this tool is used after a search, but there is no explicit when-to-use/when-not guidance and no named alternative when the caller already has a full JD.

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