A
licenseA
qualityC
maintenanceSearch current remote / work-from-home jobs by category, region, perk, or company — with ready-to-apply links.
Last updated
5
MIT
NextJobz Job Search
Server Details
Search jobs on NextJobz by keyword, location, work type, salary, and experience level.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.9/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion between overlapping purposes. The single tool's purpose is unambiguous.
Naming Consistency5/5
The sole tool follows the clear verb_noun pattern 'search_jobs', which is consistent. With a single tool, naming consistency is trivially satisfied.
Tool Count3/5
One tool is on the low end of the range. For a server dedicated to job search, a single search function may be sufficient, but it feels thin compared to typical MCP servers that offer multiple related operations.
Completeness4/5
The search tool returns comprehensive job listings with all relevant details, covering the core need of a job search server. However, there are minor gaps such as no way to fetch a specific job by ID or apply, though these may be outside the server's stated scope.
Available Tools
1 toolsearch_jobsAInspect
Search for jobs on NextJobz job portal. Returns paginated job listings with title, company, location, salary, skills, and deadline.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hybrid | No | Include hybrid jobs | |
| onSite | No | Include on-site jobs | |
| pageNo | No | Page number (1-based) | |
| remote | No | Include remote jobs | |
| search | No | Job title or company keyword to search. Default searches all jobs. | |
| contract | No | Include contract jobs | |
| fullTime | No | Include full-time jobs | |
| pageSize | No | Results per page (max 20) | |
| partTime | No | Include part-time jobs | |
| toSalary | No | Maximum salary | |
| fromSalary | No | Minimum salary | |
| internship | No | Include internship jobs | |
| companyName | No | Filter by company name | |
| jobLocation | No | Filter by job location (city or country) | |
| postedFilter | No | Filter by post date: 0=Last24Hours, 1=LastWeek, 2=LastMonth, 3=Last3Months | |
| maxExperience | No | Maximum years of experience required | |
| minExperience | No | Minimum years of experience required |
Tool Definition Quality
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It does mention that results are paginated and lists the job fields returned, which is useful. However, it does not disclose whether filters combine with AND/OR, default sorting, or any access requirements. Some transparency is present but more context could be given.
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 sentence that directly conveys purpose and the key return characteristic (paginated listings). It is concise and front-loaded, with no wasted words.
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?
Given 17 parameters, no annotations, and no output schema, the description is somewhat brief. It covers the core search functionality and return fields, but does not mention the extensive filtering options (location, salary, experience, etc.) or pagination controls. The schema covers these details, so the description is minimally complete but could provide a better overview.
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?
The input schema has 100% description coverage for all 17 parameters, so the description does not need to repeat parameter details. It adds no additional meaning beyond the schema, but the baseline is 3 when schema coverage is high.
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 action ('Search for jobs') and the resource ('NextJobz job portal'), and mentions the return format (paginated job listings with specific fields). No sibling tools exist, so differentiation is not required.
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 clearly implies when to use the tool (whenever a user needs to search for jobs on NextJobz). No alternatives or exclusions are stated, but the lack of sibling tools reduces the need for explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceSearch live startup.jobs listings with filters for role, location, and employment type, plus get job details, company profiles, hiring trends, and salary benchmarks.Last updatedMIT
- Flicense-qualityDmaintenanceProvides job search functionality using Careerjet API with features for keyword and location-based searches, advanced filtering, and support for 50+ countries and languages.Last updated3
JobsPipe MCP Serverofficial
Flicense-qualityBmaintenanceEnables searching live, normalized job postings from 30+ ATS feeds and job boards, with tools for job search, source listing, pricing plans, and Upwork jobs.Last updated