HeyLead

Overview Schema Source Related Servers Discussions Admin

profile_signals

Destructive

Compile a targeting request into LinkedIn recall and profile evidence to identify country ties or interests across full profiles. Preview scoring or list schools for targeted outreach.

Instructions

Compile a targeting request into LinkedIn recall + profile evidence.

Use this to see how HeyLead looks for country ties (school, language,
worked-in) or interests (car lovers, esoteric) on a full LinkedIn
profile. Campaigns still go through generate_icp / create_campaign.

Args:
    action: compile (default), preview, or schools (exact LinkedIn school names).
    request: e.g. "Ukrainians in the US" or "classic car lovers".
    titles: Optional comma-separated titles for recall queries.
    location_codes: Optional comma-separated LinkedIn location codes.
    profiles_json: preview only — JSON list of full profiles to score.

Input Schema

TableJSON Schema

Name	Required	Default
`action`	No	compile
`titles`	No
`request`	No
`profiles_json`	No
`location_codes`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.375Sep 18, 2026

TDQS

A4.8/5.0

Behavior4/5

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

Annotations already carry the safety profile (readOnlyHint false, destructiveHint true, openWorldHint true), so the description does not need to restate those. It adds useful behavioral context about preview mode, exact LinkedIn school name lookup, and LinkedIn recall queries, which goes beyond the schema.

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?

The description is compact, front-loaded with purpose, and uses a scannable Args block. Every sentence earns its place, including the alternative-tool routing and parameter clarifications.

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?

With an output schema present, return values are already covered. The description rounds out the remaining context: action modes, examples, preview semantics, and the boundary with campaign tools. Nothing critical is missing for an agent to select and invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for parameter semantics—and fulfills it. It explains action values, provides examples for request, marks profiles_json as 'preview only,' and clarifies that titles and location_codes are comma-separated.

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

Purpose5/5

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

The description opens with a specific verb and resource combination: 'Compile a targeting request into LinkedIn recall + profile evidence.' It further clarifies the purpose by stating it is for seeing how HeyLead looks for country ties and interests on full LinkedIn profiles, and explicitly distinguishes it from generate_icp/create_campaign.

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

Usage Guidelines5/5

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

The description explicitly says when to use this tool ('Use this to see how HeyLead looks for...') and when not to use it ('Campaigns still go through generate_icp / create_campaign'). It also documents the action variants (compile, preview, schools), giving the agent concrete usage options.

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