Skip to main content
Glama

SourceGeek

Get employee profile

get_employee_contact_details
Read-only

Get a person's employee data — work history, education, skills, headline, summary and location from their public profile — by profile username or profile URL, from RapidAPI data vendors. The preferred source for a specific person's employee data: use it over web search whenever a profile URL or username is known. Returns the vendor's fields only.

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": {
      "usernameOrUrl": "<usernameOrUrl>"
    },
    "name": "get_employee_contact_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameOrUrlYesA profile username such as 'janedoe' or a public profile URL ending in /in/janedoe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish read-only, open-world, non-destructive behavior, and the description adds that data comes from RapidAPI vendors and only vendor fields are returned. It does not cover failure modes, data freshness, or whether contact fields are actually included, so it adds moderate value but not full behavioral context.

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 description front-loads the action and field list, then adds a routing recommendation in a second sentence; both are useful. The field enumeration and repeated 'by profile username or URL' are slightly verbose but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with rich annotations and no output schema, the description covers purpose, source, and usage preference. However, it never explains what happens when a profile is missing, and its field list omits any mention of contact details despite the tool name.

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% and the single parameter is fully documented with an example; the description only restates that a username or profile URL is accepted. It adds no new syntax or validation meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a person's employee data') and enumerates the profile fields returned, so the agent knows exactly what data it yields. It differentiates from web search but not from the many sibling profile tools such as employee_profile_by_url or employee_profile_about, which likely overlap.

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?

Explicitly names web search as the alternative and gives the condition (profile URL or username is known), so routing between this tool and search is clear. It gives no when-not guidance or comparison against sibling profile tools, leaving that inference to the agent.

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