Skip to main content
Glama

SourceGeek

Get employee profile by URL

employee_profile_by_url
Read-only

Fetch a person's full public profile (headline, summary, positions, education, skills, location) from any profile URL, including hashed /in/ACoAA… URLs.

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": {
      "profileUrl": "<profileUrl>"
    },
    "name": "employee_profile_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileUrlYesFull public profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the data is public-only, the response covers a defined set of sections, and — importantly — hashed /in/ACoAA… URLs are accepted, which an agent would otherwise not assume. It omits failure behavior for malformed or private URLs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and resource, then the returned fields, then the input-format caveat. Every clause carries information and nothing is repeated from the title or schema.

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?

With no output schema, the description carries the burden of describing returns, and it does so by enumerating the profile sections. For a one-parameter read tool with full annotation coverage that is nearly complete; only the behavior on invalid or non-public URLs is left unstated.

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% and there is a single required parameter, so the baseline is already high. The description still contributes meaning the schema lacks: it clarifies that any profile URL form works, specifically including hashed /in/ACoAA… identifiers, which prevents the agent from rejecting valid inputs.

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?

The description pairs a specific verb ("Fetch") with a specific resource ("a person's full public profile") and enumerates the returned sections (headline, summary, positions, education, skills, location), which distinguishes it from siblings such as employee_profile_about or employee_profile_posts. It stops short of naming an alternative tool explicitly, so it does not reach the top of the scale.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "from any profile URL" implies the precondition (you must already have a profile URL), but the description never says when to prefer this over the many employee_profile_* siblings or what to do when you only have a name or ID. Usage is inferable rather than stated.

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