Skip to main content
Glama

AceRound AI Interview Copilot

list_job_applications

Read-only

List the user's Auto Apply applications: overall counts, then each application's id, company, role, status, and progress (50 per page). Tools that act on an application take the id from here. (Requires the user's sign-in with scope 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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds genuinely new context: page size of 50, the returned field set, and the required auth scope job_applications:read. That auth-scope disclosure is the kind of behavioral prerequisite annotations cannot express. Only the absence of pagination-termination guidance keeps it from a 5.

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?

Three short sentences, front-loaded with the resource and return contents, then the id hand-off, then the auth caveat. Every clause adds information; nothing is redundant with the title or schema.

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 usefully enumerates the returned fields and the aggregate counts, and it discloses the required scope. For a single-optional-parameter list tool this is nearly complete; it could add how total counts relate to pages, but an agent has what it needs to call it correctly.

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 bare 'page' integer with its 1-100 bounds and default carries no explanation. The description only indirectly signals pagination via '50 per page' and doesn't explain that page is a 1-based page index or what happens past the last page, so it partially but not fully compensates for the schema gap.

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?

States a specific verb and resource ('List the user's Auto Apply applications') and enumerates what comes back: overall counts plus id, company, role, status, and progress. The closing note that acting tools take the id from here implicitly separates it from the single-application get_job_application sibling.

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 establishes context ('Auto Apply applications') and a clear downstream routing rule – use this to obtain the id that mutating tools require – which is the primary reason an agent would call it. It does not explicitly contrast with get_job_application for fetching one application's detail, so it stops short of full when/when-not guidance.

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