Skip to main content
Glama

Ashby

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ashby List Candidates

ashby_list_candidates
Read-onlyIdempotent

Search candidates in your ATS. Returns names, emails, and application metadata. Use ashby_get_candidate with ID for full profile details.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoList of candidate records
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 candidate records",
+      "items": {
+        "properties": {
+          "email": {
+            "description": "Candidate email address",
+            "type": "string"
+          },
+          "id": {
+            "description": "Candidate ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Candidate full name",
+            "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": 25
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and destructiveHint false, so the description's claim 'Search candidates' aligns. However, the description adds no additional behavioral context such as pagination behavior, rate limits, or permission requirements beyond what the 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?

Two efficient sentences with no wasted words. Information is front-loaded: purpose first, then output summary, then sibling reference. Very concise.

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 output schema exists and annotations cover safety, the description is sufficient for a simple read-only search tool. It could improve by briefly noting pagination behavior, but it is complete enough for an agent to use correctly.

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% for all three parameters (cursor, _apiKey, per_page). The description does not add extra meaning beyond 'Search candidates' and mentions output fields but not parameter usage details. Baseline 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 uses a specific verb 'Search candidates' and identifies the resource 'your ATS'. It clearly distinguishes from the sibling ashby_get_candidate by noting that this tool returns names, emails, and application metadata, while the sibling provides full profile details.

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?

The description advises to use ashby_get_candidate for full profile details, which implies this tool is for broad listing/searching. It does not explicitly state when not to use or provide alternatives, but the sibling differentiation is clear and helpful for an agent.

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