Skip to main content
Glama

SourceGeek

Search job postings (precision)

precision_search_jobs
Read-only

Higher-precision CoreSignal job-posting search using the reasoning endpoint. Interprets the natural language query more carefully than the fast search and returns better-matched postings plus an explanation of how it interpreted the query. More expensive and rate-limited (~10/hour, shared with the other precision searches) — use when match quality matters. 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": "precision_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.4/5.0
Behavior5/5

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

Annotations already cover read-only/open-world safety, and the description adds substantial behavior beyond them: a shared rate limit of roughly 10/hour across precision searches, credit consumption, and the fact that results come back as CSV rather than creating a sheet. These are exactly the operational constraints an agent needs before calling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information is front-loaded: what it is, how it differs from the fast search, then cost and rate limits, then return shape. The single dense paragraph is efficient, though the return-format and credit details could be tightened slightly.

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?

With no output schema, the description supplies the return shape (CSV with Title, Company, Location, Posted, plus a suggested title) and clarifies the side effect it does not have (no sheet creation). Combined with cost and rate-limit disclosure, nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so both parameters are already documented with defaults, bounds and an example. The description adds no parameter-level detail beyond that, which matches the baseline for a fully-described schema.

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 and resource ('Higher-precision CoreSignal job-posting search using the reasoning endpoint') and explicitly contrasts it with the fast search sibling, so an agent can tell which job-search tool to pick without inspecting schemas.

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 clear selection criteria ('use when match quality matters') and an implicit tradeoff against the fast search via cost and rate limits. It stops short of an explicit exclusion such as 'avoid for bulk or high-volume lookups', so it is strong but not fully prescriptive.

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