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.
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.
Tool Definition Quality
Average 3.4/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name 'search_jobs' follows a clear verb_noun pattern, consistent with best practices.
With only one tool for a job search server, the surface is too thin; users likely need additional functionality like job details or application management.
The server lacks tools for retrieving full job details, applying, or other lifecycle operations, causing significant gaps for common workflows.
Available Tools
1 toolsearch_jobsBInspect
Search for jobs on NextJobz job portal. Returns paginated job listings with title, company, location, salary, skills, and deadline.
| 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
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description carries full burden. It mentions pagination and returned fields but lacks details on authentication, rate limits, or behavior for empty results. Minimal 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler, front-loaded with the action and resource. Highly concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 17 parameters and no output schema or annotations, the description is too brief. It does not cover how filters interact, error handling, or pagination limits beyond what's in schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. The description adds no extra parameter meaning beyond listing return fields; it does not explain how search or filters combine.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Search for jobs' and the resource 'NextJobz job portal', and mentions return fields. No siblings exist to differentiate, so it's clear enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when/when-not guidance or alternatives. Usage is implied by the verb 'search', but no context on when to use versus other tools (none exist).
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!