Skip to main content
Glama

Profile Finder

profiles
Read-only

Find and enrich professional profiles. Returns the person's name, headline, current company and title, location, summary, experience, education, skills, photo URL and LinkedIn URL. Use to learn who a professional is and what they have done. For their work email use emails; for a company rather than a person use companies. Pass linkedin_url, or first_name and last_name; company helps find the right person. Cost: 3 credits, charged only when a call succeeds.

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

Input Schema

NameRequiredDescriptionDefault
companyNoCompany name.
last_nameNoLast name.
first_nameNoFirst name.
linkedin_urlNoLinkedIn profile URL.
include_imageNoFetch profile image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing billing behavior ("Cost: 3 credits, charged only when a call succeeds") and the full payload of returned fields. It does not mention what happens on a no-match lookup or any rate/coverage limits, which keeps it short of a 5.

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 purpose then return fields then input rules and cost. The field enumeration is long but functional since there is no output schema. No filler or restated title.

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?

With zero required parameters and no output schema, the description carries the burden of explaining valid input combinations and expected return shape, and it does both. Cost semantics, which matter for an agent deciding whether to call, are also covered.

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 baseline would be 3. The description adds real meaning beyond the schema by explaining that linkedin_url alone is valid, or first_name plus last_name, and that company is a disambiguation hint rather than a requirement — the schema lists all five as optional with no such 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?

The description opens with a specific verb+resource ("Find and enrich professional profiles") and then enumerates exactly what comes back: name, headline, company, title, location, summary, experience, education, skills, photo and LinkedIn URLs. It also names the two siblings that handle adjacent needs, so an agent can distinguish it from companies and emails without opening schemas.

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?

It states the intended use ("learn who a professional is and what they have done") and gives explicit routing rules: use emails for a work email, use companies for a company rather than a person. It also specifies which input combinations are acceptable, which is the main decision an agent has to make before calling.

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.