Skip to main content
Glama

Enrich People (job history)

enrich_people

[Acquire · 3 credits/person enriched] Look up full LinkedIn profiles for up to 100 people and store their current title, company, headline and job history (every position). Job history is what get_outreach_path (coworker / alumni paths) and get_alumni_engagers search, and engagers collected from reactions/comments have none until enriched — when those tools report missing coverage they return a _meta.next_step with the exact person_ids to pass here. Pass person_ids (people.id from any engager / path tool) and/or linkedin_urls. Costs 3 credits per person successfully enriched. People you already have (connected to you: they engaged with your posts, are in your campaigns or segments, or you pulled or enriched them) who were enriched in the last 90 days are skipped for free unless refresh=true; anyone else is looked up and charged normally; failed or not-found lookups are free. The balance must cover 3 × the people to be looked up (after skips and max_credits) before anything runs; you are charged only for successes.

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

Input Schema

NameRequiredDescriptionDefault
refreshNoRe-enrich people enriched within the last 90 days (bypasses the cache)
person_idsNopeople.id UUIDs to enrich (1-100)
max_creditsNoSpend cap. At most floor(max_credits / 3) people are looked up; the rest come back skipped_budget.
linkedin_urlsNoLinkedIn profile URLs to enrich; people not yet in the graph are added

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-idempotent, open-world, non-destructive, but the description goes well beyond them: 3 credits per successful person, 90-day skip for already-known people, refresh bypasses the cache, failed/not-found lookups are free, and a pre-flight balance check must cover 3 × lookups. It does not describe the success/failure response shape, but the billing and caching behavior is unusually thorough.

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?

The cost tag is front-loaded and every sentence carries non-redundant information (trigger, inputs, cost, cache rules, billing precheck). It is a dense single paragraph, though, so the skip/billing rules are harder to scan than they would be as bulleted lines.

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?

For a paid, non-idempotent enrichment mutation with no output schema, the definition covers the inputs' provenance, the trigger from sibling tools, skip/refresh rules, budget guarding, and failure charging. An agent has everything needed to call it safely without a trial run.

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?

Schema coverage is 100%, so baseline would be 3; the description adds real meaning on top by specifying that person_ids are people.id values from any engager or path tool, and that the balance requirement is computed after skips and max_credits. It does not add format detail for linkedin_urls beyond what the schema says.

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?

Names a specific verb and resource ('Look up full LinkedIn profiles') plus a scope cap (up to 100) and exactly what is stored (current title, company, headline, every position). It also distinguishes itself from get_outreach_path and get_alumni_engagers by explaining that it supplies the job-history data those tools search.

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?

Gives an explicit trigger condition: when get_outreach_path or get_alumni_engagers report missing coverage, they return a _meta.next_step with the person_ids to pass here. It also tells the agent that reaction/comment engagers have no history until enriched, and clarifies the refresh-vs-cache decision.

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