Skip to main content
Glama

100Hires - AI ATS & Recruitment Software

by com.100hires
OverviewDiscussionsAdmin

List jobs

hires_list_jobs
Read-only

List jobs filtered by status, creation/update time, department or search query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSearch title or internal title
pageNo
sizeNo
viewNosummary
statusNoFrom hires_list_statuses, e.g. Public, Draft, Archived
includeNoEmbed: workflow, hiring_team, pipeline_stages
company_idNo
department_idNoFrom hires_list_departments
updated_afterNoUnix seconds or ISO-8601; for incremental sync
created_at_endNoUnix seconds or ISO-8601
created_at_startNoUnix seconds or ISO-8601

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / company_id / description
      Removed value: -"Filter by company ID (required only for multi-company API keys)"
    • changedInput schema / properties / created_at_end / description
      Previous value: -"Return only jobs created at or before this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated."New value: +"Unix seconds or ISO-8601"
    • changedInput schema / properties / created_at_start / description
      Previous value: -"Return only jobs created at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated."New value: +"Unix seconds or ISO-8601"
    • changedInput schema / properties / department_id / description
      Previous value: -"Filter jobs by department ID (from GET /taxonomy/departments)"New value: +"From hires_list_departments"
    • changedInput schema / properties / include / description
      Previous value: -"Comma-separated related resources to embed: workflow, hiring_team, pipeline_stages"New value: +"Embed: workflow, hiring_team, pipeline_stages"
    • removedInput schema / properties / page / description
      Removed value: -"Page number (default 1)"
    • changedInput schema / properties / q / description
      Previous value: -"Search by job title or internal title (partial match)"New value: +"Search title or internal title"
    • removedInput schema / properties / size / description
      Removed value: -"Page size (default 20)"
    • changedInput schema / properties / status / description
      Previous value: -"Filter by job status name (from GET /taxonomy/statuses, e.g. Public, Draft, Archived)"New value: +"From hires_list_statuses, e.g. Public, Draft, Archived"
    • changedInput schema / properties / updated_after / description
      Previous value: -"Return only jobs updated at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated. Use for incremental sync."New value: +"Unix seconds or ISO-8601; for incremental sync"
    • removedInput schema / properties / view / description
      Removed value: -"Response shape. Default `summary` excludes heavy fields (description HTML, indeed_posting_data, ai_scoring_criteria) and embedded relations — recommended for list operations. Use `full` only when description or include=workflow/hiring_team/pipeline_stages is genuinely needed; call hires_get_job for a single full record."
  2. Changed6 schema fields changed
    • changedInput schema / properties / created_at_end / description
      Previous value: -"Return only jobs created at or before this Unix timestamp (seconds)"New value: +"Return only jobs created at or before this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated."
    • changedInput schema / properties / created_at_end / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / created_at_start / description
      Previous value: -"Return only jobs created at or after this Unix timestamp (seconds)"New value: +"Return only jobs created at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated."
    • changedInput schema / properties / created_at_start / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
    • changedInput schema / properties / updated_after / description
      Previous value: -"Return only jobs updated after this Unix timestamp (seconds). Use for incremental sync."New value: +"Return only jobs updated at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but truncated. Use for incremental sync."
    • changedInput schema / properties / updated_after / type
      Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "default": "summary",
+  "description": "Response shape. Default `summary` excludes heavy fields (description HTML, indeed_posting_data, ai_scoring_criteria) and embedded relations — recommended for list operations. Use `full` only when description or include=workflow/hiring_team/pipeline_stages is genuinely needed; call hires_get_job for a single full record.",
+  "enum": [
+    "summary",
+    "full"
+  ],
+  "type": "string"
+}
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations show read-only/no destructive effects)Skip? Actually description doesn't contradict; it simply doesn't add much beyond filters. With readOnlyHint in annotations, the bar is lower)Skip. no contradiction. Maybe 3: It doesn't mention pagination or output shape, but annotations cover safety.

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?

Single clear sentence, front-loaded with the verb and core filters. No filler or redundant restatement of schema.

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?

Adequate for a read-only list operation, but with 11 parameters, no output schema, and no mention of pagination or included subresources, an agent may not know the return shape or how to page through results.

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?

Description maps to q, status, department_id, and time-window params (created_at_start/end, updated_after), which helps. But it omits page/size, view, include, and company_id, and schema coverage is only 64%, so the description doesn't fully compensate.

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?

Clearly states it lists jobs and names the main filter dimensions (status, time, department, search). It does not explicitly distinguish itself from siblings like get_job or get_career_job, but the verb 'list' plus the filter scope make the core purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this over alternatives (e.g., get_job, get_career_job) or what prerequisites apply. The agent must infer usage from the name and filters.

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

All 100Hires - AI ATS & Recruitment Software toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources