Skip to main content
Glama

Search talent outside Clera

searchExternalTalent

Search the wider talent market: people who are NOT in Clera's network and have not opted in to hearing from companies.

Use searchCandidates first. That searches Clera's own pool of candidates who are open to opportunities, it has its own daily budget, and those people can be introduced to you. Only reach for this tool when Clera's pool genuinely does not cover the brief, or the user explicitly asks to look outside Clera.

Costs one of the company's 17 daily search credits, so make each one count: set the filters you actually need rather than running several broad passes. Returns at most 15 people.

Returns no email and no phone, only profile data. To get contact details for one of these people, pass their linkedinUrl to lookupContact.

Call listExternalTalentFilters if you are unsure which values a filter accepts.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "filters": "<filters>"
    },
    "name": "searchExternalTalent"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
filtersYes

Output Schema

NameRequiredDescriptionDefault
profilesYes
searchIdYes
totalResultsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (openWorld=false-destructive, not idempotent), it discloses the scarce-cost model (1 of 17 daily credits), the result cap of 15, the fact that no email or phone is returned, and that inputs/results are privately recorded. These are exactly the traits an agent must know before spending the credit, and none are recoverable from the schema.

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?

Five short paragraphs, each front-loading a distinct decision: what it searches, when to prefer the sibling, cost, output limits, and follow-up routing. There is no filler and no sentence that could be deleted without losing an operational constraint.

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?

An output schema exists, yet the description still surfaces the two return facts an agent needs for planning (15-person cap, no contact data) plus the exact path to get contact data. Combined with cost, exclusion scope, and filter discovery, an agent has everything required to invoke it correctly on the first try.

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?

With only 50% schema coverage across a large nested filter object, the description compensates strategically: it warns to set only the filters actually needed instead of running several broad passes, points to listExternalTalentFilters for accepted values, and references linkedinUrl as the hand-off key to lookupContact. It does not explain individual filters, which is the remaining gap, but the discovery pointer covers it adequately.

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?

It names a specific verb and a precisely bounded resource: 'Search the wider talent market: people who are NOT in Clera's network and have not opted in to hearing from companies.' The negative scoping distinguishes it cleanly from searchCandidates without either schema being opened.

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

Usage Guidelines5/5

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

Explicit routing: 'Use searchCandidates first' with the reasons (own pool, its own daily budget, introducible), then 'Only reach for this tool when Clera's pool genuinely does not cover the brief, or the user explicitly asks.' It also names lookupContact for follow-up and listExternalTalentFilters for filter values, so no alternative is left to inference.

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