Skip to main content
Glama

Summarize an external search

getSearchInsights
Read-onlyIdempotent

Summarize who an external search (from searchExternalTalent) found: top locations, current companies, experience spread, highlight badges, and three takeaways.

Free: it spends no external search and contacts nobody. Use it to answer "what does this pool look like" before deciding to shortlist or start outreach.

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": {
      "searchId": "<searchId>"
    },
    "name": "getSearchInsights"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
searchIdYesThe search id returned by searchExternalTalent.

Output Schema

NameRequiredDescriptionDefault
badgesYes
basedOnYes
takeawaysYes
topCompaniesYes
topLocationsYes
totalResultsYes
coversWholePoolYes
experienceBucketsYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the description correctly focuses on what they cannot express: that the call is free (spends no external search credits) and contacts nobody. The privacy note about recording inputs and results adds a further disclosure about data handling, though it reads as boilerplate.

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?

Front-loads the purpose and contents, then the cost/usage rationale, with no wasted framing. The closing privacy sentence is generic boilerplate that does not help tool selection, though it may be a required disclosure.

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?

An output schema exists, so return values need not be explained, and the description still previews the summary sections, which aids selection. Cost, side effects, and input provenance are all covered; only explicit guidance on alternatives or failure cases 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, including orgId's multi-org conditionality, are already documented in the schema. The description adds only the provenance of searchId (returned by searchExternalTalent) and nothing about orgId, which is the expected baseline when the schema does the heavy lifting.

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 (summarize) and resource (an external search's result pool), and enumerates the actual contents of the summary: top locations, current companies, experience spread, highlight badges, and three takeaways. It also ties the input back to searchExternalTalent, so an agent can distinguish it from search tools in the sibling list.

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 usage context: 'Use it to answer "what does this pool look like" before deciding to shortlist or start outreach', which establishes ordering relative to downstream actions. It does not explicitly state when NOT to use it or name a specific alternative for the summarization job, so it falls 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