Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

NicheDB: Find Profile by LinkedIn

nichedb_find_profile_by_linkedin
Read-onlyIdempotent

[NicheDB] The public profile a LinkedIn profile or company URL belongs to (linkedin.com/in/… or /company/…), or null. LinkedIn only: profiles are never looked up by email.

Served by NicheDB (https://nichedb.dev/docs/mcp).

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": {
      "url": "<url>"
    },
    "name": "nichedb_find_profile_by_linkedin"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA LinkedIn URL, e.g. https://www.linkedin.com/in/ada

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavior beyond them: the result may be null when no profile matches, and lookup is restricted to LinkedIn URLs, never email. It does not describe what the returned profile object contains, but no output schema exists, so that is a modest gap.

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?

Two short sentences plus a provider line, with the scoping constraint and the null outcome both front-loaded. The opening clause is a sentence fragment and reads awkwardly, but nothing is wasted.

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?

For a single-parameter, annotation-rich lookup with no output schema, the description covers the input domain, the null case, and the exclusion. There is nothing an agent needs in order to call this correctly that is missing.

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 the single parameter is documented with an /in/ example. The description still adds meaning by stating that company URLs (/company/…) are also accepted, which the schema example does not show. That is genuine semantic value 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?

The description states a specific resolution operation: map a LinkedIn person or company URL to the NicheDB public profile it belongs to. That is a clear verb+resource, and it is distinguishable from search-type siblings. It stops short of naming a sibling (e.g. nichedb_get_profile or nichedb_search_profiles), so the differentiation is only implicit.

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 implied rather than stated: you supply a LinkedIn URL and get the owning profile. The one explicit constraint — 'LinkedIn only: profiles are never looked up by email' — usefully rules out an email-based path. No alternative tool is named for when you lack a LinkedIn URL or want to search by name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Profullstack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources