Skip to main content
Glama

Coresignal

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Coresignal Employee

coresignal_employee
Read-onlyIdempotent

Find a person's professional profile by name (+company) via Coresignal — returns title, current company, location, LinkedIn URL, work experience and education. LinkedIn-adjacent people data. Example: coresignal_employee({ name: "Patrick Collison", company: "Stripe", _apiKey: "your-key" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name of the person, e.g. "Patrick Collison".
_apiKeyYesCoresignal API key (BYO). Sign up + start a trial at coresignal.com.
companyNoOptional company name to disambiguate, e.g. "Stripe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-coresignal-api-key",
+    "company": "Stripe",
+    "name": "Patrick Collison"
+  },
+  {
+    "_apiKey": "your-coresignal-api-key",
+    "name": "Sam Altman"
+  }
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds specifics about returned data (title, company, location, LinkedIn URL, experience, education) and notes it's 'LinkedIn-adjacent', providing useful context.

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?

Two sentences plus an example, front-loaded with purpose. No unnecessary words.

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?

While no output schema exists, the description lists returned fields and provides an example. It covers the main aspects for a simple lookup, though pagination and error handling are omitted.

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 covers all parameters (100% coverage). The description adds an example call showing usage, but does not add extra semantic meaning beyond what the schema provides.

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 clearly states the tool finds a person's professional profile by name and optionally company, listing returned fields. However, it does not differentiate from siblings like entity_profile or resolve_entity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as coresignal_company or other people discovery tools. The description only states what it does, not the best context for use.

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

All Coresignal 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