Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

linkedin_b2b_executive_finder_verified_email

Read-onlyIdempotent

LinkedIn B2B Executive Search & MX Email Enricher: Real-time structured data extraction feed for LinkedIn B2B Executive Search & MX Email Enricher.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "linkedin_b2b_executive_finder_verified_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety, external reach, and repeatability are covered without the description. The only added phrase, 'Real-time structured data extraction feed', is vague and adds no information about latency, rate limits, authentication, or credit consumption. No contradiction with annotations, but nothing beyond them.

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

Conciseness2/5

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

It is short, but the entire second half repeats the first half word for word, so the length buys nothing. The front-loaded portion is a label, not a capability statement.

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

Completeness2/5

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

No output schema exists, so the description must carry the burden of explaining what comes back — e.g. whether emails are MX-verified, what fields accompany each executive, and what the record cap means in practice. It explains none of this, leaving the agent unable to predict results from a call.

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?

Only maxResults exists, and schema description coverage is 100% with a clear 'Maximum number of records to return' description. The description adds no meaning about pagination, defaults, or result caps, so the baseline of 3 applies.

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

Purpose2/5

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

The description restates the title almost verbatim: 'LinkedIn B2B Executive Search & MX Email Enricher: Real-time structured data extraction feed for LinkedIn B2B Executive Search & MX Email Enricher.' It names a resource domain but never states in plain terms what the tool returns (executive contact records with verified emails?) or how it differs from siblings like b2b_leads_finder_verified_emails or linkedin_profile_company_enricher_no_cookies. This is closer to tautology than a specific verb+resource statement.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. Many siblings also produce verified B2B emails, and the description gives the agent no basis for choosing this one over b2b_leads_finder_verified_emails or b2b_company_decision_maker_email_finder.

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