Skip to main content
Glama

Resolve People

resolve_people
Read-onlyIdempotent

[Read · free] Resolve up to 200 LinkedIn profile URLs and/or person_ids to people in your Flux graph, free. Each result has person_id, the stored LinkedIn URL, matched_via (exact / canonical / member_id / public_identifier / none), name, current title and company, and coverage: has_positions (job history on file), enriched_at, engaged_with_you (engagements on your posts), in_campaigns (how many of your campaigns include them) and connected_via (engaged / campaign / segment / pulled). Only people connected to you resolve: someone who engaged with posts you can see, is in your campaigns or segments, or whom you pulled or enriched. Anyone else comes back as matched_via "none", the same as an unknown URL. _meta.next_step is the enrich_people call (with its credit cost) that saves the unmatched URLs and fills job history for matched people who lack it. Use it to triage a list of URLs before spending credits. Pure DB read, no LinkedIn pull, 0 credits.

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

Input Schema

NameRequiredDescriptionDefault
person_idsNopeople.id UUIDs. 1-200.
linkedin_urlsNoLinkedIn profile URLs, any form (vanity, /in/ACo…, trailing slash, utm params). 1-200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context: it is a pure DB read with no LinkedIn pull at 0 credits, the matched_via vocabulary (exact / canonical / member_id / public_identifier / none), and the _meta.next_step handoff to enrich_people. That is materially more than the annotations supply.

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-loaded with the read/free tag and the core verb, then layered with result fields and the escalation path. It is dense rather than padded, but 'free' and '0 credits / no LinkedIn pull' restate the same fact at both ends, so a sentence could be tightened.

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?

No output schema exists, and the description compensates fully by enumerating every returned field (person_id, stored URL, matched_via, name, title, company, has_positions, enriched_at, engaged_with_you, in_campaigns, connected_via) and the _meta.next_step. An agent has everything needed to call it and interpret the response.

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 the parameter formats (UUIDs, any URL form, 1–200 items) are already documented. The description adds the combinational semantics that the schema leaves implicit — the two inputs may be used 'and/or' together — plus the outcome when an input cannot be resolved. Useful, though not deep per-parameter guidance.

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 ('Resolve ... LinkedIn profile URLs and/or person_ids to people in your Flux graph') with the batch limit (200) up front. The scope constraint — only people already connected to you resolve — further separates it from sibling lookup tools like linkedin_people_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?

Explicitly says when to use it ('Use it to triage a list of URLs before spending credits') and names the next action, the enrich_people call, with its credit cost. It also names the exclusion: anyone not connected to you returns matched_via 'none', so the agent knows this tool cannot conjure unknown profiles.

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