Skip to main content
Glama

list_job_sources

Read-only

List the job boards and ATS platforms JobsPipe documents, collected or not. Use it to check whether a platform such as Workday is covered before searching; it returns no jobs. Returns, per platform, name, slug, a summary that says when it is not collected, coverage when it is, and page URL.

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

Input Schema

NameRequiredDescriptionDefault
name_containsNoPart of a platform name, e.g. workday. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name_contains / description
      Previous value: -"Optional case-insensitive substring to filter sources by name (e.g. \"workday\")."New value: +"Part of a platform name, e.g. workday. Omit for all."
  2. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only behavior, and the description adds meaningful context beyond that: the tool returns platform metadata only, not jobs. It also discloses per-platform return fields including non-collection summary, coverage, and page URL.

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?

The description is three short sentences, front-loaded with purpose, then usage guidance, then return shape. Every sentence contributes distinct information with no filler.

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?

The tool is simple, its single parameter is fully documented, and there is no output schema, so the description usefully supplies the return shape and key fields. An agent has enough context to call it correctly and interpret the result.

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%, and the optional name_contains parameter is already documented with an example and 'Omit for all' behavior. The description adds no further filtering semantics beyond the schema, so the baseline 3 applies.

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 ('List') and resource ('job boards and ATS platforms JobsPipe documents'), including the scope 'collected or not'. The clause 'returns no jobs' distinguishes it from job search behavior and prevents misuse.

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?

Gives a clear when-to-use case: checking whether a platform such as Workday is covered before searching. It also implies a when-not by saying it returns no jobs, but it does not name the alternative search tool explicitly, so it falls short of a full 5.

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