Skip to main content
Glama
Sign In
DrawOffer MCP Server

DrawOffer MCP Server

by ql-link
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

列出岗位

list_jobs
Read-only

Retrieve and search saved job postings with keyword filtering and pagination to quickly find specific roles in your account.

Instructions

列出账号里保存的岗位 JD，支持关键词搜索和分页。

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

Input Schema

NameRequiredDescriptionDefault
limitNo每页条数，默认 20
cursorNo上一页返回的 next_cursor
keywordNo按岗位名、公司、城市、描述等搜索

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that results are limited to the account's own saved jobs and are paginated, but says nothing about default ordering, page size behavior beyond the schema, or cursor expiry.

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?

One compact sentence with the verb and resource front-loaded and no filler. The trailing '支持关键词搜索和分页' is slightly redundant with the schema but still aids scanning.

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?

A simple all-optional read tool with full schema coverage and annotations that cover the safety profile; no output schema is needed because next_cursor is described in the cursor parameter itself. Nothing essential to correct invocation is missing.

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 coverage is 100%, so all three parameters are already documented with their own descriptions. The description only restates that keyword search and pagination exist, adding no syntax, matching semantics, or defaults beyond what the schema provides.

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 (列出岗位 JD) with scope (账号里保存的) and mentions keyword search and pagination. It does not explicitly distinguish itself from the sibling get_job / create_job, so it falls short of a 5.

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?

Usage is implied: use this to browse the saved jobs in the account, optionally narrowing with a keyword. It never says when to use get_job for a single job's detail, nor does it state any prerequisites or exclusions, so the agent must infer sibling routing.

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

Deploy Server

Other Tools