Skip to main content
Glama

Ashby

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ashby Get Job

ashby_get_job
Read-onlyIdempotent

Get full job posting by ID. Returns description, requirements, hiring stage, and applicant count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYesAshby job ID
_apiKeyYesAshby API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoJob ID
titleNoJob title
descriptionNoFull job description
hiringStageNoCurrent hiring stage for this job
requirementsNoJob requirements
applicantCountNoTotal number of applicants

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "applicantCount": {
+      "description": "Total number of applicants",
+      "type": "number"
+    },
+    "description": {
+      "description": "Full job description",
+      "type": "string"
+    },
+    "hiringStage": {
+      "description": "Current hiring stage for this job",
+      "type": "string"
+    },
+    "id": {
+      "description": "Job ID",
+      "type": "string"
+    },
+    "requirements": {
+      "description": "Job requirements",
+      "type": "string"
+    },
+    "title": {
+      "description": "Job title",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-ashby-api-key",
+    "jobId": "job_67890"
+  }
+]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, indicating a safe, repeatable read operation. The description adds specifics on returned data (description, requirements, etc.), providing transparency beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that front-loads the action ('Get full job posting by ID') and lists key return fields. It is efficient but could be slightly more detailed.

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 low complexity (2 params, no enums) and presence of an output schema, the description adequately covers the tool's purpose and return fields. It is sufficient for an agent to understand functionality.

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% with clear descriptions for jobId and _apiKey. The description does not add additional parameter information beyond what the schema already provides, meeting the baseline.

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 gets a full job posting by ID, listing specific return fields like description and applicant count. This distinguishes it from sibling tool 'ashby_list_jobs' which lists jobs without full details.

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 when you have a job ID, but it does not explicitly state when to use this tool over alternatives like 'ashby_list_jobs' or other tools. No exclusion criteria or context provided.

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