Skip to main content
Glama

run_wellfound_jobs_search

Search Wellfound jobs by role and location to get listings with title, pay, locations, description, and hiring company details.

Instructions

Search Wellfound jobs by role and location: job title, pay, locations, description and the hiring company (size, stage, tags). 1 point per returned record.

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": {
      "role": "<role>",
      "location": "<location>"
    },
    "name": "run_wellfound_jobs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole (slug). e.g. software-engineer
locationYesLocation (slug). e.g. san-francisco
max_itemsNoMax items (up to 250)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the pricing model ('1 point per returned record'), which is real added value, but says nothing about pagination behavior (start_page/max_items), rate limits, or auth requirements.

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?

A single front-loaded sentence that packs the resource, query dimensions, returned fields, and cost note without waste. Well sized for a search tool.

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?

There is no output schema, but the description compensates by enumerating the returned fields (job title, pay, locations, description, company size/stage/tags), and the schema fully covers inputs. Only the pagination and cost-scaling mechanics are left implicit.

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 the schema already documents all four parameters including slug examples. The description restates role and location but adds no format or syntax detail beyond what the schema provides, so the baseline 3 applies.

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 (search) and resource (Wellfound jobs) and enumerates what each record contains (title, pay, locations, company size/stage/tags). An agent can distinguish it from siblings like run_wellfound_companies and run_wellfound_locations, though it never names them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by role and location' implies when the tool applies and matches the two required params, but there is no explicit when-to-use/when-not guidance and no reference to alternative search tools or pagination strategy.

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

Deploy Server

Other Tools