Usajobs

Search

search

Read-onlyIdempotent

Search USAJOBS announcements. Returns title, agency, location, salary band, posting/closing dates.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page
`remote`	No	Telework/remote only
`keyword`	No	Free-text — title + description + agency name
`location`	No	City/state (e.g. "San Francisco, CA")
`organization`	No	Agency code or name (e.g. "VATA" or "Veterans")
`pay_grade_low`	No	"GS5", "GS9", "SES", ...
`pay_grade_high`	No
`position_title`	No	Restrict to job title field
`results_per_page`	No	1-500 (default 25)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`JobData`	No	Array of job posting objects
`SearchResult`	No	Search result metadata and job postings

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "keyword": "software engineer",
+    "location": "Washington, DC",
+    "results_per_page": 25
+  },
+  {
+    "organization": "VATA",
+    "pay_grade_high": "GS12",
+    "pay_grade_low": "GS9",
+    "position_title": "Data Analyst",
+    "remote": true
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from USAJOBS API",
+  "properties": {
+    "JobData": {
+      "description": "Array of job posting objects",
+      "items": {
+        "description": "Individual job posting",
+        "properties": {
+          "MatchedObjectDescriptor": {
+            "description": "Job posting details",
+            "properties": {
+              "AnnouncementNumber": {
+                "description": "USAJOBS announcement number",
+                "type": "string"
+              },
+              "ApplicationCloseDate": {
+                "description": "ISO date when applications close",
+                "type": "string"
+              },
+              "JobGrade": {
+                "description": "Pay grade codes",
+                "items": {
+                  "properties": {
+                    "Code": {
+                      "description": "Pay grade code",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "LocationName": {
+                "description": "Work locations",
+                "items": {
+                  "type": "string"
+                },
+                "type": "array"
+              },
+              "OrganizationName": {
+                "description": "Federal agency name",
+                "type": "string"
+              },
+              "PositionScheduleTypeCode": {
+                "description": "Work schedule type",
+                "type": "string"
+              },
+              "PositionTitle": {
+                "description": "Job title",
+                "type": "string"
+              },
+              "PublicationStartDate": {
+                "description": "ISO date when posting opened",
+                "type": "string"
+              },
+              "SalaryBasis": {
+                "description": "Salary basis code (e.g. PA for per annum)",
+                "type": "string"
+              },
+              "SalaryRangeFrom": {
+                "description": "Minimum annual salary",
+                "type": "number"
+              },
+              "SalaryRangeTo": {
+                "description": "Maximum annual salary",
+                "type": "number"
+              },
+              "TeleworkIndicator": {
+                "description": "Whether telework is available",
+                "type": "boolean"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Unique job posting ID",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "SearchResult": {
+      "description": "Search result metadata and job postings",
+      "properties": {
+        "PageNumber": {
+          "description": "Current page number",
+          "type": "integer"
+        },
+        "SearchResultCount": {
+          "description": "Total number of matching results",
+          "type": "integer"
+        },
+        "SearchResultCountAll": {
+          "description": "Total count across all pages",
+          "type": "integer"
+        },
+        "UserArea": {
+          "description": "User-specific search result details",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations establish readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful return-field context, but it does not elaborate on pagination behavior, result ordering, or the implications of openWorldHint. Given annotation coverage, this adds some but not rich behavioral context.

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, front-loaded sentence. It states the action, the resource, and the return fields without redundancy or unnecessary words. Every phrase earns its place.

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 presence of an output schema and high schema parameter coverage, the description covers the core purpose and return values adequately. It lacks guidance on combining multiple optional filters or pagination nuances, but these are not critical for a search tool with well-structured schema metadata.

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 high (89%), so the input schema already documents most parameters. The description adds no parameter-specific semantics beyond listing return fields, which does not compensate for the small schema gap. 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 states a specific verb and resource ('Search USAJOBS announcements') and enumerates the return fields (title, agency, location, salary band, posting/closing dates). This clearly distinguishes it from sibling tools like get_job (retrieving a single announcement) or list_agencies.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that for a specific job ID, get_job should be used, or that list_agencies handles agency lookups. The only contextual clues come from sibling tool names, which the agent must infer.

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

All Usajobs tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.