Skip to main content
Glama

Work Insiders

Search recruiting and HR tools

workinsiders_search_tools
Read-onlyIdempotent

Searches the Work Insiders directory of 1,350+ recruiting, HR, sales prospecting and AI tools by free text and filters: category, first party MCP server, API, free plan, free trial, AI-native and maximum starting price. Returns up to 25 tools per page, each with its starting price, flags and Work Insiders page link. Full detail on one tool comes from workinsiders_get_tool.

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": "workinsiders_search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort order. Default relevance (editor picks first when there is no query).
limitNo
queryNoFree text such as a tool name or a job to be done ("LinkedIn outreach", "AI interview notes"). Optional.
offsetNoNumber of results to skip. next_offset in a response is the start of the next page.
has_apiNoOnly tools with a public API.
has_mcpNoOnly tools whose vendor runs its own (first party) MCP server.
categoryNoCategory slug or name, for example "ats", "sourcing" or "Email finders". The full list comes from workinsiders_list_categories.
ai_nativeNoOnly tools that ship real AI features.
free_planNoOnly tools with a free plan or free tier.
free_trialNoOnly tools with a confirmed free trial.
max_monthly_priceNoMaximum starting price in USD per month. Tools with a free plan count as $0. Per seat prices count one seat, yearly prices are divided by 12, and quote-only or pay-per-use tools are left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restating. The description adds real value beyond that: page size capped at 25, the fields returned per result (starting price, flags, page link), and the handoff to get_tool. It still says nothing about ranking behaviour or what happens when filters match nothing, which is where a higher score would come from.

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?

Three sentences, front-loaded with the search scope, then the return shape, then the handoff to get_tool. The middle sentence carries a dense but useful enumeration of filters; nothing is padding, though the filter list borders on duplicating the schema.

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?

With 11 optional parameters and no output schema, the description usefully compensates by describing page size and the per-result payload. Pagination mechanics are partly deferred to the schema's next_offset note, and result ordering nuance is left to the sort enum, which are minor gaps for a filtered-search tool.

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 91%, so the schema already carries nearly all parameter meaning, including the enum, defaults, min/max and the price normalization rules. The description's filter list largely restates schema properties, though 'first party MCP server' and 'maximum starting price' do add a little plain-language gloss.

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 ('Searches the Work Insiders directory of 1,350+ recruiting, HR, sales prospecting and AI tools') plus the two search modes (free text and filters). It also names the sibling that serves the adjacent need, so an agent can distinguish discovery from detail lookup 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?

The final sentence explicitly routes single-tool lookups to workinsiders_get_tool, giving a clear boundary. It does not cover other plausible alternatives such as compare_tools or find_alternatives, and there are no explicit exclusions, so it falls just short of a 5.

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