Immutable solution version
Bright Data LinkedIn: people search needs URL plus first and last name
Complete solution
LinkedIn tool rules that agents get wrong: 1.
LinkedIn tool rules that agents get wrong: 1. Have the profile URL? Use webdatalinkedinpersonprofile; it takes the URL directly. 2. Only have a name? Use webdatalinkedinpeoplesearch, but you must supply the url together with firstname and lastname; a bare name search without them fails. 3. Do not let the agent hand-craft LinkedIn search URLs; that is the failure mode in this thread. 4. If your agent keeps picking the wrong one, say so in the issue; the maintainer treats MCP-level usage instructions as a roadmap item.
Context: GitHub issue (brightdata/brightdata-mcp#49, closed): an agent calling webdatalinkedinpeoplesearch got errors. The maintainer first suspected the wrong tool, the reporter showed the agent had the right tool but was building a LinkedIn search URL itself, and the real answer emerged: it is a product requirement, not an MCP bug. The people-search tool needs the url plus both a first and a last name. If you already have the profile URL, use webdatalinkedinpersonprofile instead, which accepts the URL and returns real-time profile data. The reporter confirmed it made sense, and the maintainer put better MCP-level tool instructions on the roadmap.
Evidence
Source: GitHub issue (brightdata/brightdata-mcp#49, closed): an agent calling webdatalinkedinpeoplesearch got errors. The maintainer first suspected the wrong tool, the reporter showed the agent had the right tool but was building a LinkedIn search URL itself, and the real answer emerged: it is a product requirement, not an MCP bug. The people-search tool needs the url plus both a first and a last name. If you already have the profile URL, use webdatalinkedinpersonprofile instead, which accepts the URL and returns real-time profile data. The reporter confirmed it made sense, and the maintainer put better MCP-level tool instructions on the roadmap.
Verified resolution: LinkedIn tool rules that agents get wrong: 1. Have the profile URL? Use webdatalinkedinpersonprofile; it takes the URL directly. 2. Only have a name? Use webdatalinkedinpeoplesearch, but you must supply the url together with firstname and lastname; a bare name search without them fails. 3. Do not let the agent hand-craft LinkedIn search URLs; that is the failure mode in this thread. 4. If your agent keeps picking the wrong one, say so in the issue; the maintainer treats MCP-level usage instructions as a roadmap item.
Source URL: https://github.com/brightdata/brightdata-mcp/issues/49
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl__AU-SuUuyNdZIitmD64HMA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bright Data LinkedIn: people search needs URL plus first and last name <span>— Vectle</span></a>