Skip to main content
Glama

Ashby

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ashby List Applications

ashby_list_applications
Read-onlyIdempotent

Search job applications across positions. Returns candidate name, applied job, application stage, and submission date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response
_apiKeyYesAshby API key
per_pageNoNumber of applications per page (default 50)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoList of applications
nextCursorNoPagination cursor for next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "nextCursor": {
+      "description": "Pagination cursor for next page",
+      "type": "string"
+    },
+    "results": {
+      "description": "List of applications",
+      "items": {
+        "properties": {
+          "candidateName": {
+            "description": "Name of the applying candidate",
+            "type": "string"
+          },
+          "id": {
+            "description": "Application ID",
+            "type": "string"
+          },
+          "jobId": {
+            "description": "Job ID applied for",
+            "type": "string"
+          },
+          "jobTitle": {
+            "description": "Title of the job applied for",
+            "type": "string"
+          },
+          "stage": {
+            "description": "Current application stage",
+            "type": "string"
+          },
+          "submittedAt": {
+            "description": "ISO 8601 timestamp of application submission",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-ashby-api-key"
+  },
+  {
+    "_apiKey": "your-ashby-api-key",
+    "per_page": 100
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds minimal extra transparency beyond listing returned fields. No mention of pagination behavior or authentication requirements beyond what schema provides.

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 a single concise sentence (15 words) that front-loads the action and outputs. No redundant information.

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?

Given the tool has an output schema, the description need not fully document return values. It covers the main output fields. However, it could mention that results are paginated, but overall adequate.

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 each parameter is already documented. The tool description adds no additional meaning to parameters beyond what the schema provides. Baseline score of 3 is appropriate.

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?

The description clearly states the tool's function: 'Search job applications across positions' and specifies the returned fields (candidate name, applied job, application stage, submission date). This distinguishes it from sibling tools like ashby_list_candidates and ashby_list_jobs.

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 searching all applications but does not provide explicit guidance on when to use this tool versus alternatives (e.g., ashby_list_candidates for candidates). No when-not-to-use advice.

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

All Ashby toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources