Skip to main content
Glama

job_list

Retrieve job listings from Ashby ATS with filtering by status and pagination support. Use this tool to browse open, closed, or archived positions in your hiring pipeline.

Instructions

List all jobs (open, closed, archived). Supports cursor pagination and status filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status(es). If omitted, returns all non-Draft jobs.
limitNoMax results per page (default/max 100)
cursorNoCursor for next page of results

Implementation Reference

  • The `handle_call_tool` function routes the `job_list` tool call by looking up its associated endpoint in `TOOL_ENDPOINT_MAP` and calling it via the `ashby.post` method.
    @server.call_tool()
    async def handle_call_tool(name: str, arguments: dict[str, Any]) -> list[types.TextContent]:
        """Route tool calls to the correct Ashby endpoint, passing arguments directly."""
        endpoint = TOOL_ENDPOINT_MAP.get(name)
        if not endpoint:
            return [types.TextContent(type="text", text=f"Unknown tool: {name}")]
    
        try:
            # Pass arguments straight through -- tool schemas already use Ashby's
            # camelCase param names so no translation is needed.
            response = ashby.post(endpoint, data=arguments if arguments else None)
            return [types.TextContent(type="text", text=json.dumps(response, indent=2))]
        except requests.exceptions.HTTPError as e:
            error_body = ""
            if e.response is not None:
                try:
                    error_body = e.response.text
                except Exception:
                    pass
            return [
                types.TextContent(
                    type="text",
                    text=f"Ashby API error on {endpoint}: {e}\n{error_body}",
                )
            ]
        except Exception as e:
            return [types.TextContent(type="text", text=f"Error calling {endpoint}: {e}")]
  • Registration of the `job_list` tool in the `TOOLS` list, including its schema definition.
    types.Tool(
        name="job_list",
        description="List all jobs (open, closed, archived). Supports cursor pagination and status filtering.",
        inputSchema={
            "type": "object",
            "properties": {
                "status": {
                    "type": "array",
                    "items": {"type": "string", "enum": ["Draft", "Open", "Closed", "Archived"]},
                    "description": "Filter by status(es). If omitted, returns all non-Draft jobs.",
                },
                "limit": {"type": "integer", "description": "Max results per page (default/max 100)"},
                "cursor": {"type": "string", "description": "Cursor for next page of results"},
            },
        },
    ),
  • `TOOL_ENDPOINT_MAP` defines the mapping between the tool name `job_list` and the Ashby API endpoint `/job.list`.
    TOOL_ENDPOINT_MAP = {
        "job_list": "/job.list",
        "job_info": "/job.info",
        "job_search": "/job.search",
        "candidate_list": "/candidate.list",
        "candidate_search": "/candidate.search",
        "candidate_info": "/candidate.info",
        "candidate_create": "/candidate.create",
        "candidate_create_note": "/candidate.createNote",
        "candidate_list_notes": "/candidate.listNotes",
        "candidate_add_tag": "/candidate.addTag",
        "candidate_tag_list": "/candidateTag.list",
        "application_list": "/application.list",
        "application_info": "/application.info",
        "application_create": "/application.create",
        "application_change_stage": "/application.change_stage",
        "interview_stage_list": "/interviewStage.list",
        "interview_plan_list": "/interviewPlan.list",
        "interview_list": "/interview.list",
        "interview_info": "/interview.info",
        "department_list": "/department.list",
        "user_list": "/user.list",
        "source_list": "/source.list",
        "archive_reason_list": "/archiveReason.list",
        "location_list": "/location.list",
    }
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses pagination behavior ('cursor pagination') and filtering capability, but doesn't mention rate limits, authentication requirements, error conditions, or what the response format looks like. It adequately describes core functionality but lacks operational details.

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?

Two concise sentences with zero waste. First sentence states purpose and scope, second sentence adds key behavioral capabilities. Every word earns its place and information is front-loaded appropriately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with 3 parameters and no output schema, the description covers basic purpose and key behaviors (pagination, filtering). However, without annotations or output schema, it should ideally mention response format, error handling, or authentication needs to be more complete for agent usage.

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 100%, so the schema already fully documents all three parameters. The description mentions 'status filtering' and 'cursor pagination' which align with parameters, but adds no additional semantic context beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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?

The description clearly states the verb ('List') and resource ('jobs') with scope ('all jobs (open, closed, archived)'). It distinguishes from sibling 'job_search' by focusing on listing rather than searching, but doesn't explicitly differentiate from 'job_info' which retrieves a single job.

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?

The description implies usage for listing jobs with pagination and filtering, but doesn't explicitly state when to use this tool versus alternatives like 'job_search' or 'job_info'. No guidance on prerequisites or exclusions is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PlenishAI/mcp-ashby'

If you have feedback or need assistance with the MCP directory API, please join our Discord server