Skip to main content
Glama

List User Job Listings

list_user_job_listings
Read-onlyIdempotent

List the authenticated user's saved job listings (GET /api/job-listings?includeDescription=false). Returns minor details only: id, company (name/logo/etc.), position/role (job title), source, createdAt. Does not return the job posting body (description / jobPosition) — that floods context; call get_user_job_listing with an id when you need the full description. Present each option as company name + role, wait for the user to pick one, then pass that id as jobListingId to get_cover_letter_cost / create_cover_letter (omit companyName/role/jobPosition). Prefer this before asking for a full manual company/role/job description when the user may already have the job saved.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
kindYes
countYes
adviceYes
listingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that: it enumerates the concrete return fields (id, company, position, source, createdAt), explains that the description body is deliberately omitted because it floods context, and prescribes a human-in-the-loop selection step.

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?

Dense but front-loaded: the core purpose comes first, then return shape, then the alternative tool, then the workflow. It is somewhat packed into one long paragraph with multiple parentheticals, so it could be split for readability, but no sentence is wasted.

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?

With an output schema and full annotation coverage, the description only needs to supply purpose, return scope, and workflow guidance — all of which it does. Nothing an agent needs to invoke this correctly and hand off to the next tool is missing.

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?

The tool takes zero parameters, so there is no per-parameter semantics to add; baseline 4 applies. The `id`/`jobListingId` mention refers to parameters of other tools, which is useful routing context but not this tool's own input.

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 authenticated user's saved job listings") and even names the endpoint. It explicitly contrasts with the sibling get_user_job_listing by saying it returns minor details only and not the posting body, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing rules: prefer this before asking the user for a manual company/role/job description, and call get_user_job_listing with an id only when the full description is needed. It also spells out the downstream path (pass the chosen `id` as `jobListingId` to get_cover_letter_cost / create_cover_letter, omitting companyName/role/jobPosition).

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