Skip to main content
Glama

SourceGeek

Search job postings

fast_search_jobs
Read-only

Search CoreSignal for job postings using a natural language query. Use this for finding open roles by title, company, location, or hiring signals (e.g. which companies are hiring for a role). Sorting can be requested inside the query (supported fields: last_updated, company_employees_count). Returns the matched postings as CSV (Title, Company, Location, Posted) plus a suggested title — it does not create a sheet. Spends the workspace's credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fast_search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRequested number of job postings to return (1-20). Defaults to 10 when omitted. The data source returns at most 20 results per search.
queryYesNatural language search query, e.g. 'Senior backend engineer roles at fintech companies in Berlin, sorted by last_updated'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: the CSV shape and columns, the extra "suggested title" in the response, the no-sheet side effect, and the fact that the call spends workspace credits. It stops short of describing result caps or credit cost magnitude, but the credit warning is the key non-obvious cost signal.

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?

Front-loaded with purpose, then use cases, then sort syntax, then return format and cost — a sensible information order with no filler. Each sentence contributes a distinct fact (query usage, sorting, output shape, no sheet, credits).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by naming the returned format and columns plus the suggested title. Combined with the credit-cost disclosure and in-query sorting rules, an agent has what it needs to call this correctly without opening anything else.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and the baseline is 3. The description adds genuinely new semantics by explaining that sorting is expressed inside the query string and naming the supported sort fields (last_updated, company_employees_count) — information the schema does not carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search CoreSignal for job postings using a natural language query") and enumerates the searchable dimensions (title, company, location, hiring signals). It does not, however, distinguish itself from the several sibling job-search tools (precision_search_jobs, employee_search_jobs), leaving that differentiation to the caller.

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?

Gives concrete usage context — finding open roles by title/company/location, or answering "which companies are hiring for a role" — and records the sorting mechanism so the caller knows where to put ordering intent. It adds one explicit exclusion ("it does not create a sheet"), but never states when to prefer a sibling job-search tool instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources