Skip to main content
Glama

application_list

Retrieve and filter candidate applications from the Ashby hiring pipeline by job ID, status, or creation date using pagination.

Instructions

List applications. Can filter by jobId and/or status. Uses cursor pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdNoFilter by job ID (UUID)
statusNoFilter by application status
createdAfterNoOnly return applications created after this timestamp (ms since epoch)
limitNoMax results per page (default/max 100)
cursorNoCursor for next page

Implementation Reference

  • The tool call handler `handle_call_tool` uses `TOOL_ENDPOINT_MAP` to route tool calls to the appropriate Ashby API endpoint. The execution logic is defined generically by calling `ashby.post(endpoint, data=arguments)`.
    @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))]
  • The definition and input schema for the `application_list` tool.
    types.Tool(
        name="application_list",
        description="List applications. Can filter by jobId and/or status. Uses cursor pagination.",
        inputSchema={
            "type": "object",
            "properties": {
                "jobId": {"type": "string", "description": "Filter by job ID (UUID)"},
                "status": {
                    "type": "string",
                    "enum": ["Active", "Hired", "Archived", "Lead"],
                    "description": "Filter by application status",
                },
                "createdAfter": {
                    "type": "integer",
                    "description": "Only return applications created after this timestamp (ms since epoch)",
                },
                "limit": {"type": "integer", "description": "Max results per page (default/max 100)"},
  • The mapping of `application_list` to its corresponding Ashby API endpoint path `/application.list` in `TOOL_ENDPOINT_MAP`.
        "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",
    }
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively adds context beyond the input schema by specifying 'Uses cursor pagination,' which is crucial for understanding how to handle large result sets. However, it doesn't mention rate limits, authentication needs, or what the return format looks like (e.g., structure of listed applications).

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 extremely concise with three short sentences that are front-loaded and waste no words. Each sentence adds value: the first states the core action, the second specifies filtering options, and the third discloses pagination behavior.

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?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the action, filtering, and pagination, but lacks details on return values, error handling, or performance considerations (e.g., default limits). With no output schema, more guidance on response structure would be helpful.

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 documents all parameters thoroughly. The description adds minimal value by mentioning filtering by 'jobId and/or status,' which is implied in the schema but not explicitly stated. No additional syntax or format details are provided beyond what the schema offers.

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 ('applications'), making the purpose immediately understandable. It distinguishes from siblings like 'application_info' (single application) and 'candidate_list' (different resource), though it doesn't explicitly contrast with 'application_change_stage' or 'application_create' which have different actions.

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 through 'Can filter by jobId and/or status,' suggesting when filtering might be appropriate, but doesn't explicitly state when to use this tool versus alternatives like 'candidate_list' or 'candidate_search' for related data. 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