Enrich Layer MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

enrich_job_count

Read-only

Count job postings matching keyword, location, job type, flexibility, experience level, and posting time. Use filters to quantify hiring activity for any role or company.

Instructions

Get the number of job postings matching your criteria. Cost: 2 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "enrich_job_count"
  }
}

Input Schema

Name	Required	Description
`when`	No	When the job was posted.
`geo_id`	No	geo_id of the location to search, e.g. 92000000
`keyword`	No	Keyword to search for, e.g. engineer
`job_type`	No	Nature of the job.
`search_id`	No	search_id of the company, e.g. 2790400
`flexibility`	No	Job flexibility.
`experience_level`	No	Experience level needed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 19, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already cover read-only and open-world behavior, so the bar is lower. The description adds the useful 'Cost: 2 credits' detail, but it does not disclose other behavioral aspects such as whether results are capped, how criteria are combined, or what the exact return format is beyond 'number.'

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 short, front-loaded sentences that state the core function and cost with no filler. Every word adds value, and the cost note is a practical detail that would otherwise be missing.

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?

For a simple count tool with seven optional parameters and no output schema, the description is minimally adequate but leaves gaps: it does not state whether all filters are optional, whether the count is exact or approximate, or describe the response shape beyond 'number.' The strong schema coverage partially compensates.

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%, with each parameter and enum having descriptive text, so the schema carries the semantic load. The description only adds a generic 'matching your criteria' phrase and does not enhance understanding of specific parameters like geo_id or search_id.

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's function with a specific verb ('Get') and resource ('number of job postings'), making it evident this is a count operation. This distinguishes it from sibling tools like enrich_job_search and enrich_job_profile, which imply list/detail operations.

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 explicit guidance on when to use this tool versus alternatives like enrich_job_search, nor does it mention exclusions or prerequisites. The only hint is 'matching your criteria,' which implies usage but does not explain scenarios or provide comparison with sibling tools.

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