A
licenseA
qualityC
maintenanceEnables real-time job search across thousands of companies' open roles from Greenhouse, Lever, Ashby, and SmartRecruiters, with full-text filtering and company-specific queries, no API key required.
2
MIT
LaraBench
Server Details
Search Laravel jobs, remote roles, Laravel news, and package releases in real time.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
2 toolssearch_laravel_jobsSearch Laravel jobsARead-onlyInspect
Search recent Laravel jobs indexed by LaraBench, including full description, salary, seniority, and employment type. Results are limited to the last 30 days. Each job carries a LaraBench detail page and, when the source published one, the original apply URL.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of jobs to return. | |
| query | No | Free-text search across job title, company, and description. | |
| countries | No | Country or remote-region filters. | |
| locations | No | Location text filters. | |
| seniority | No | Seniority filters. | |
| technologies | No | Technology filters such as laravel, vue, inertia, livewire, or react. | |
| salaryMinimum | No | Minimum disclosed salary, in the currency given by salaryCurrency. | |
| salaryCurrency | No | Three-letter currency code (e.g. USD, EUR, GBP) to pair with salaryMinimum. | |
| employmentTypes | No | Employment type filters. | |
| workArrangement | No | Restrict results to a single work arrangement. Defaults to any. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| asOf | Yes | |
| results | Yes | |
| larabenchUrl | Yes | |
| totalAvailable | Yes | |
| freshnessWindowDays | Yes |
TDQS
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and destructiveHint false, and the description adds useful behavioral context such as the 30-day time limit and that each job includes a LaraBench detail page and possibly an original apply URL. This goes beyond the annotations by clarifying data scope and return characteristics, though it doesn't mention pagination or ordering.
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 two sentences, front-loaded with the core purpose and key result details. Every clause adds value: the first sentence states the resource and result content, the second adds temporal and URL context. There is no redundancy or filler.
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?
The description provides essential context about the data source (LaraBench) and time bound (last 30 days), which is valuable given the tool's 10 optional parameters. Since an output schema exists and the annotations cover safety, the description is sufficient for a useful overview, though it could mention default ordering or filter combination semantics for full completeness.
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 100%, so the baseline is 3. The description does not add extra meaning to the parameters; it only mentions that results include certain fields, which doesn't explain parameter usage. The schema already documents each parameter adequately, so no deduction is needed.
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 searches Laravel jobs indexed by LaraBench, and specifies the data returned (description, salary, seniority, employment type). It also distinguishes from the sibling tool search_laravel_news by focusing on jobs rather than news, making the 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 Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for querying recent Laravel jobs, and the sibling tool's existence suggests a contrast, but there is no explicit when-to-use or alternative statement. The usage context is clear enough from the description, but it does not explicitly say when not to use it or offer alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_laravel_newsSearch Laravel news and releasesARead-onlyInspect
Search recent Laravel ecosystem news and package releases indexed by LaraBench. Results are limited to the last 7 days. Each item carries a LaraBench detail page and the original article or release notes URL.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of items to return. | |
| query | No | Free-text search across article and release titles and summaries. | |
| types | No | Restrict results to articles, package releases, or both. Defaults to both. | |
| topics | No | Topic filters such as laravel, php, vue, jobs, or packages. | |
| channel | No | Release channel to include. stable excludes prereleases, preview returns only prereleases, all returns both. Defaults to stable. | |
| sources | No | News source filters. | |
| packages | No | Composer or npm package filters. | |
| projects | No | Project filters such as laravel, inertia, livewire, filament, or pest. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| results | Yes | Article and release items are shaped differently; see the type field. |
| generatedAt | Yes | |
| larabenchUrl | Yes | |
| totalAvailable | Yes | |
| freshnessWindowDays | Yes |
TDQS
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral context beyond annotations: results are limited to the last 7 days and each item includes a LaraBench detail page plus an original URL, which helps set expectations.
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?
Two sentences, front-loaded with the action and resource, no filler. Every clause adds value: the 7-day restriction and the detail/original URL links are the key operational notes.
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?
For a search tool with 8 optional parameters and an output schema, the description supplies the crucial temporal constraint and result item composition. It does not mention default ordering or empty-query behavior, but the open-world annotation and schema compensate for that gap.
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 covers 100% of parameters with meaningful descriptions, so the description does not need to repeat parameter-level details. It adds high-level context about time window and result structure, but no additional per-parameter semantics beyond the schema. 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?
Description states a specific verb and resource: 'Search recent Laravel ecosystem news and package releases indexed by LaraBench.' It clearly distinguishes from the sibling tool search_laravel_jobs by focusing on news/releases rather than jobs.
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 communicates domain scope: Laravel news and releases, not jobs. It does not explicitly mention the sibling tool as an alternative, but the differentiation is evident from the stated resource and 'recent' timeframe.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- Changed
search_laravel_jobs2 fields changed- added
Output schema / properties / results / items / properties / sourceUrlAdded value: +{ + "description": "Where to apply on the original site, when the source published one.", + "format": "uri", + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / results / items / properties / url / descriptionAdded value: +"The LaraBench job detail page."
- Changed
search_laravel_news2 fields changed- added
Output schema / properties / results / items / properties / sourceUrlAdded value: +{ + "description": "The original article for articles, or the release notes or registry page for releases.", + "format": "uri", + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / results / items / properties / url / descriptionAdded value: +"The LaraBench detail page."
1 tool update
- Changed
search_laravel_jobs3 fields changed- added
Output schema / properties / results / items / properties / descriptionAdded value: +{ + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / results / items / properties / employmentTypeAdded value: +{ + "type": [ + "string", + "null" + ] +} - added
Output schema / properties / results / items / properties / seniorityAdded value: +{ + "type": [ + "string", + "null" + ] +}
2 tool updates
- First observed
search_laravel_jobs - First observed
search_laravel_news
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Search DevRel tools, communities, jobs, events, CFPs, and guides from devrel.directory.
Search job postings, companies, and technology stacks across 10M+ companies.
Search a live index of millions of open jobs from employer career sites and 100+ ATS platforms.
Search and apply to real jobs, browse companies, and read tech news via Datronis's live data.
Related MCP Servers
- AlicenseAqualityDmaintenanceSearch 21 sources in one call — GitHub, npm, PyPI, arXiv, HN, X, Reddit, and more. No API keys to juggle, structured JSON back.21171MIT
JobsPipe MCP Serverofficial
FlicenseNot gradedqualityBmaintenanceEnables searching live, normalized job postings from 30+ ATS feeds and job boards, with tools for job search, source listing, pricing plans, and Upwork jobs.-- AlicenseNot gradedqualityBmaintenanceEnables natural-language job search and aggregation from multiple recruitment websites with zero configuration, providing filtered results and standardized output for AI assistants.69ISC
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
The two tools target distinct domains: Laravel jobs and Laravel news. There is no overlap in purpose, and each tool's description clearly differentiates its scope.
Naming Consistency5/5
Both tools follow the same verb_noun pattern: search_laravel_jobs and search_laravel_news. The naming is perfectly symmetric and predictable.
Tool Count4/5
With only 2 tools, the server is minimal but appropriate for its focused niche of Laravel job and news search. It's slightly thin but not inadequate.
Completeness4/5
The two search tools cover the apparent main functions of the server. A possible gap is lack of direct retrieval by ID, but search results include detail page URLs, making the surface reasonably complete.