Skip to main content
Glama

SourceGeek

Get employee profile with posts

employee_profile_full_with_posts
Read-only

Fetch a person's full public profile, connection/follower counts and recent posts in one call (2 credits).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
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.8/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, open-world behavior, so the bar is lower. The description still adds genuine operational context by disclosing the credit cost (2 credits) and that it returns a *public* profile, which informs budgeting and scope decisions. It stops short of describing auth requirements or result ordering.

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 front-loaded sentence that names the resource, enumerates the returned components, and tucks the cost at the end. There is no filler or redundancy.

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?

For a 2-parameter read tool with no output schema, the description covers what is returned, the cost, and the public scope, while the schema handles parameter constraints. Only the trade-off against narrower sibling tools remains unstated.

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?

With 100% schema description coverage, the baseline is 3. The description adds no parameter-level detail beyond the schema: it does not explain the username-vs-URL duality or clarify how limit interacts with the aggregation behavior, both of which are already handled by the schema text.

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 uses a concrete verb ("Fetch") with a clearly enumerated payload: full public profile, connection/follower counts, and recent posts. The phrase "in one call" implicitly separates it from narrower siblings such as employee_profile_posts or employee_profile_with_recommendations, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the aggregate choice when both profile and posts are needed, reinforced by the "in one call" framing. There is no explicit when-to-use, when-not-to-use, or named alternative to route against the many sibling profile tools.

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