Dice MCP
Server Details
Dice MCP: Search for tech jobs on Dice.com
- 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 4.5/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_jobs' has a singular, well-defined purpose focused on job searching, making it impossible for an agent to misselect among non-existent alternatives.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'search_jobs' follows a clear verb_noun pattern (search + jobs), and with no other tools to compare against, there are no deviations or inconsistencies in naming conventions.
A single tool is too few for a job search domain, which typically requires operations like filtering, saving, or applying to jobs. While the tool is well-described, the server lacks essential complementary tools (e.g., get_job_details, apply_job, save_search), making it feel incomplete and under-scoped for practical agent workflows.
The tool set is severely incomplete for job searching. It only provides search functionality, with no tools for retrieving detailed job information, managing applications, or interacting with job listings beyond initial search. This creates significant gaps that will hinder agents in performing comprehensive job-related tasks, leading to potential dead ends in workflows.
Available Tools
1 toolsearch_jobsJob SearchARead-onlyInspect
Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.
Use this tool when users want to find jobs, search employment opportunities, or explore job openings. DO NOT use for: applying to jobs, submitting applications, or making employment decisions.
LLM USAGE INSTRUCTIONS:
ALWAYS provide the keyword parameter (required)
When presenting results to users, include BOTH the job details URL (detailsPageUrl) AND the company page URL (companyPageUrl) for each job
Use location to find geographically relevant positions
Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)
Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)
Default jobs_per_page is reasonable, increase for comprehensive searches
IMPORTANT - AI DISCLOSURE REQUIREMENT: When presenting job search results to users, you MUST include an appropriate disclosure that these results were retrieved using AI assistance. Example disclosure language: "These job listings were found using AI-powered search. Please review all job details carefully and verify information directly with employers before applying."
This tool provides job listing data only. Final employment decisions should always involve human judgment and direct review of complete job postings.
Args: keyword: The job keyword or title to search for (required) location: Geographic location for the job search (city, state, country) radius: Search radius from the specified location (minimum 1.0) radius_unit: Unit for search radius. Options: 'mi', 'km', 'miles', 'kilometers' jobs_per_page: Number of jobs to return per page (1-100, default handled by API) page_number: Page number for pagination (1-based, default is 1) posted_date: Filter by posting date. Options: 'ONE' (1 day), 'THREE' (3 days), 'SEVEN' (7 days) workplace_types: Workplace arrangements. Options: 'Remote', 'On-Site', 'Hybrid' employment_types: Employment types. Options: 'FULLTIME', 'CONTRACTS', 'PARTTIME', 'THIRD_PARTY' employer_types: Employer types. Options: 'Direct Hire', 'Recruiter', 'Other' willing_to_sponsor: Filter for employers willing to sponsor work authorization (boolean) easy_apply: Filter for jobs with easy application process (boolean) fields: Specific fields to include in response (optional, returns all fields by default)
Returns: JobSearchResult: Contains: - data: List of JobDisplayFields with job details including: * detailsPageUrl: Direct link to full job posting * companyPageUrl: Link to company profile page * title, summary, salary, location, employmentType, etc. - meta: Search metadata with pagination info and facet results - _links: Pagination navigation links
Raises: Exception: If API call fails or input validation errors occur
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | ||
| radius | No | ||
| keyword | Yes | ||
| location | No | ||
| easy_apply | No | ||
| page_number | No | ||
| posted_date | No | ||
| radius_unit | No | ||
| jobs_per_page | No | ||
| employer_types | No | ||
| workplace_types | No | ||
| employment_types | No | ||
| willing_to_sponsor | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| data | No | Array of job listings matching the search criteria |
| meta | No | Metadata about the search results and pagination |
| _links | No | Pagination navigation links |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds significant behavioral context beyond what annotations provide. While annotations indicate readOnlyHint=true and destructiveHint=false, the description adds important context about required disclosure ('MUST include an appropriate disclosure that these results were retrieved using AI assistance'), presentation requirements ('include BOTH the job details URL... AND the company page URL'), and limitations ('provides job listing data only... Final employment decisions should always involve human judgment'). No contradictions with annotations exist.
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?
The description is comprehensive but somewhat lengthy and could be more efficiently structured. While all content is relevant, the 'LLM USAGE INSTRUCTIONS' and 'IMPORTANT - AI DISCLOSURE REQUIREMENT' sections could be integrated more seamlessly. The information is front-loaded with purpose and usage guidelines, but the overall structure feels segmented rather than flowing naturally.
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?
Given the tool's complexity (13 parameters, 0% schema description coverage), the description provides excellent contextual completeness. It covers purpose, usage guidelines, behavioral context, parameter semantics, and output expectations. The presence of an output schema means the description doesn't need to explain return values in detail, and it appropriately focuses on how to use the tool effectively. The disclosure requirements and limitations are particularly valuable additions.
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?
With 0% schema description coverage, the description carries the full burden of parameter documentation. It provides meaningful context for several parameters: keyword ('required'), location ('geographically relevant positions'), workplace_types ('e.g., workplace_types=['Remote'] for remote work'), posted_date ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days), and jobs_per_page ('reasonable, increase for comprehensive searches'). While not all 13 parameters are individually explained, the description compensates well for the schema's lack of descriptions.
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 tool's purpose: 'Search for job listings by keyword, location, and filters.' It specifies the verb ('search'), resource ('job listings'), and scope (search criteria). The description distinguishes this tool from alternatives by explicitly stating what it does NOT do ('DO NOT use for: applying to jobs, submitting applications, or making employment decisions').
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?
The description provides explicit usage guidelines: 'Use this tool when users want to find jobs, search employment opportunities, or explore job openings.' It also includes clear exclusions: 'DO NOT use for: applying to jobs, submitting applications, or making employment decisions.' This gives the AI agent specific guidance on when to use this tool versus other potential actions.
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!