Skip to main content

Find your role first

by click.findyourrolefirst

Overview Discussions Admin

Count matching jobs

count_jobs

Read-onlyIdempotent

Count the roles a search_jobs call would match, up to 1,000. Free: no jobs returned, no credits used.

    Use it to narrow a search (add a location, exclude words, posted_within_hours) before paying for results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Whole words matched in the title or company, e.g. "product manager" or "quant". Empty for any.
`roles`	No	Several titles at once, matching any, e.g. ["Product Manager", "Software Engineer"]. Up to 40.
`family`	No	"product_adjacent" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it.	any
`remote`	No	Only remote roles.
`source`	No	Only roles from one source (gh is Greenhouse), or "any".	any
`exclude`	No	Leave out titles containing any of these words, e.g. "senior staff intern".
`location`	No	One country ("United States", "UK", "India"), or a city or state as written. Empty for anywhere.
`locations`	No	Several places at once, matching any, e.g. ["United States", "London", "Remote"]. Up to 8.
`experience`	No	Years of experience the posting asks for; any of "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (we read the posting and it names none) and "unchecked" (not read yet, or no text to read: many big-company and Workday roles). Include both unless you mean to drop them.
`posted_within_hours`	No	Only roles posted within this many hours; 0 for any time.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "any",
-  "gh",
-  "ashby",
-  "lever",
-  "workday",
-  "amazon",
-  "microsoft",
-  "netflix",
-  "apple",
-  "google",
-  "meta",
-  "eightfold",
-  "jibe",
-  "phenom",
-  "atlassian",
-  "successfactors"
-]New value: +[
+  "any",
+  "gh",
+  "ashby",
+  "lever",
+  "workday",
+  "amazon",
+  "microsoft",
+  "netflix",
+  "apple",
+  "google",
+  "meta",
+  "eightfold",
+  "jibe",
+  "phenom",
+  "atlassian",
+  "successfactors",
+  "radancy"
+]

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "any",
-  "gh",
-  "ashby",
-  "lever",
-  "workday",
-  "amazon",
-  "microsoft",
-  "netflix",
-  "apple",
-  "google",
-  "meta",
-  "eightfold",
-  "jibe",
-  "phenom",
-  "atlassian"
-]New value: +[
+  "any",
+  "gh",
+  "ashby",
+  "lever",
+  "workday",
+  "amazon",
+  "microsoft",
+  "netflix",
+  "apple",
+  "google",
+  "meta",
+  "eightfold",
+  "jibe",
+  "phenom",
+  "atlassian",
+  "successfactors"
+]

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "any",
-  "gh",
-  "ashby",
-  "lever",
-  "workday",
-  "amazon",
-  "microsoft",
-  "netflix",
-  "apple",
-  "google",
-  "meta",
-  "eightfold",
-  "jibe",
-  "phenom"
-]New value: +[
+  "any",
+  "gh",
+  "ashby",
+  "lever",
+  "workday",
+  "amazon",
+  "microsoft",
+  "netflix",
+  "apple",
+  "google",
+  "meta",
+  "eightfold",
+  "jibe",
+  "phenom",
+  "atlassian"
+]

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "any",
-  "gh",
-  "ashby",
-  "lever",
-  "workday",
-  "amazon",
-  "microsoft",
-  "netflix",
-  "apple",
-  "google",
-  "meta",
-  "eightfold"
-]New value: +[
+  "any",
+  "gh",
+  "ashby",
+  "lever",
+  "workday",
+  "amazon",
+  "microsoft",
+  "netflix",
+  "apple",
+  "google",
+  "meta",
+  "eightfold",
+  "jibe",
+  "phenom"
+]

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / source / enum

Previous value: -[
-  "any",
-  "gh",
-  "ashby",
-  "lever",
-  "workday",
-  "amazon",
-  "microsoft",
-  "netflix",
-  "apple",
-  "google",
-  "meta"
-]New value: +[
+  "any",
+  "gh",
+  "ashby",
+  "lever",
+  "workday",
+  "amazon",
+  "microsoft",
+  "netflix",
+  "apple",
+  "google",
+  "meta",
+  "eightfold"
+]

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / experience / description

Previous value: -"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (about a third of postings don't say; include it unless you mean to drop them)."New value: +"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (we read the posting and it names none) and \"unchecked\" (not read yet, or no text to read: many big-company and Workday roles). Include both unless you mean to drop them."

changedInput schema / properties / experience / items / enum

Previous value: -[
-  "0-1",
-  "1-3",
-  "3-5",
-  "5-8",
-  "8+",
-  "not_stated"
-]New value: +[
+  "0-1",
+  "1-3",
+  "3-5",
+  "5-8",
+  "8+",
+  "not_stated",
+  "unchecked"
+]

Changed10 schema fields changedOct 1, 2026

addedInput schema / properties / exclude / description

Added value: +"Leave out titles containing any of these words, e.g. \"senior staff intern\"."

addedInput schema / properties / experience / description

Added value: +"Years of experience the posting asks for; any of \"0-1\", \"1-3\", \"3-5\", \"5-8\", \"8+\", \"not_stated\" (about a third of postings don't say; include it unless you mean to drop them)."

addedInput schema / properties / family / description

Added value: +"\"product_adjacent\" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it."

addedInput schema / properties / location / description

Added value: +"One country (\"United States\", \"UK\", \"India\"), or a city or state as written. Empty for anywhere."

addedInput schema / properties / locations / description

Added value: +"Several places at once, matching any, e.g. [\"United States\", \"London\", \"Remote\"]. Up to 8."

addedInput schema / properties / posted_within_hours / description

Added value: +"Only roles posted within this many hours; 0 for any time."

addedInput schema / properties / query / description

Added value: +"Whole words matched in the title or company, e.g. \"product manager\" or \"quant\". Empty for any."

addedInput schema / properties / remote / description
```
Added value: +"Only remote roles."
```

addedInput schema / properties / roles / description

Added value: +"Several titles at once, matching any, e.g. [\"Product Manager\", \"Software Engineer\"]. Up to 40."

addedInput schema / properties / source / description

Added value: +"Only roles from one source (gh is Greenhouse), or \"any\"."

First observedOct 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint, so the safety profile is covered. The description adds value beyond those fields: the 1,000-result cap and the billing behavior (free, no jobs returned, no credits used), which an agent needs in order to decide whether to call this instead of search_jobs.

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 short sentences, cap and cost stated first, then the usage rationale. No wasted text.

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 free counting tool with rich annotations and an output schema, the description covers the essentials: what is counted, the cap, and the cost model. Nothing critical is missing, though it could note that results are an approximation of search_jobs matching.

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 all 10 parameters are already documented with examples and enum semantics. The description adds only a passing reference to location, exclude and posted_within_hours as narrowing levers, so the baseline 3 applies.

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?

States a specific verb+resource (count roles) and precisely scopes it as an equivalent of what search_jobs would match, with a hard cap of 1,000. Naming search_jobs lets an agent distinguish it from get_job, list_my_jobs, and the other siblings without opening a schema.

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?

Explicitly says to use it to narrow a search (add a location, exclude words, posted_within_hours) before paying for results, which effectively positions it as the free preview of search_jobs. It lacks an explicit when-not/no-op statement, but the routing condition is clear.

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

All Find your role first tools Inspect

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources