Skip to main content
Glama

面灵AI 面试助手

list_job_applications

Read-only

列出用户的网申投递记录:总体统计与每条投递的投递 ID、公司、岗位、投递状态、进展(每页 50 条)。按投递操作的工具所需的投递 ID 取自这里。(需要用户授权,范围 job_applications:read)

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_job_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real value beyond them by disclosing pagination (50 per page) and the required authorization scope job_applications:read. It does not describe what the overall statistics contain or how many pages typically exist, but the operational prerequisites an agent needs are present.

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 content is packed into one dense sentence plus an authorization note, with the core purpose front-loaded and no filler. The parenthetical auth scope is slightly tacked-on but still earns its place.

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 carries the return-shape burden and does so by listing the returned fields and mentioning overall statistics. Auth scope and pagination are covered; only minor gaps remain around statistics contents and paging limits.

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?

There is one parameter (page) with 0% schema description coverage, so the schema only shows type, default, and bounds. The description compensates partially by stating the page size of 50 records, which lets an agent reason about pagination, but it never explains the page parameter itself or what happens past the last page.

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

Purpose5/5

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

The description gives a specific verb and resource (list the user's job application records) and enumerates what each record contains: application ID, company, position, status, and progress. It also implicitly separates itself from the singular getter siblings by stating that the IDs used by application-operating tools come from this list.

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

Usage Guidelines4/5

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

It clearly signals the key workflow: call this tool first to obtain the application ID needed by downstream tools that act on an application. It does not state when to use get_job_application instead of this list, nor any exclusion, so the guidance is clear but not fully routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources