Social Fetch

Resolve LinkedIn person

linkedin_live_person_resolve_v2

Read-only

Resolve a LinkedIn handle to a person entity id.

Input Schema

TableJSON Schema

Name	Required	Description
`trim`	No	Ignored if this tool does not support it.
`urls`	No	Alias for `handle`. Prefer `handle`.
`user`	No	Alias for `handle`. Prefer `handle`.
`limit`	No	Ignored if this tool does not support it.
`handle`	No	LinkedIn profile handle. Not an organization slug. A /in/{handle} URL is accepted.
`offset`	No	Ignored if this tool does not support it.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`pageSize`	No	Ignored if this tool does not support it.
`userName`	No	Alias for `handle`. Prefer `handle`.
`username`	No	Alias for `handle`. Prefer `handle`.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`maxResults`	No	Ignored if this tool does not support it.
`profileUrl`	No	Alias for `handle`. Prefer `handle`.
`linkedinUrl`	No	Alias for `handle`. Prefer `handle`.
`max_results`	No	Ignored if this tool does not support it.
`screen_name`	No	Alias for `handle`. Prefer `handle`.
`conversation_id`	No	Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedSep 21, 2026

addedInput schema / properties / limit

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / linkedinUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / linkedinUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / profileUrl / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / profileUrl / type
```
Removed value: -"string"
```

addedInput schema / properties / screen_name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / screen_name / type
```
Removed value: -"string"
```

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / urls

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `handle`. Prefer `handle`."
+}

addedInput schema / properties / user / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / user / type
```
Removed value: -"string"
```

addedInput schema / properties / userName / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / userName / type
```
Removed value: -"string"
```

addedInput schema / properties / username / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]

removedInput schema / properties / username / type
```
Removed value: -"string"
```

Changed6 schema fields changedSep 20, 2026

changedInput schema / properties / handle / description

Previous value: -"LinkedIn profile handle. Not an organization slug."New value: +"LinkedIn profile handle. Not an organization slug. A /in/{handle} URL is accepted."

removedInput schema / properties / handle / maxLength
```
Removed value: -200
```
removedInput schema / properties / handle / minLength
```
Removed value: -1
```
removedInput schema / properties / handle / pattern
```
Removed value: -"^[\\p{L}\\p{N}_.%-]+$"
```

addedInput schema / properties / linkedinUrl

Added value: +{
+  "description": "Alias for `handle`. Prefer `handle`.",
+  "type": "string"
+}

addedInput schema / properties / profileUrl

Added value: +{
+  "description": "Alias for `handle`. Prefer `handle`.",
+  "type": "string"
+}

Changed1 schema field changedSep 19, 2026

changedInput schema / properties / handle / description

Previous value: -"LinkedIn profile handle or organization slug."New value: +"LinkedIn profile handle. Not an organization slug."

AddedSep 19, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description adds no behavioral context beyond the annotations. While readOnlyHint=true and openWorldHint=true cover the safety profile, the description does not disclose any additional traits such as acceptable URL formats, error behavior, or what happens when an unknown handle is supplied—details an agent would need for robust invocation.

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?

One sentence with zero wasted words. The core input/action/output are packed into a single front-loaded statement, making it instantly scannable and memorable.

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?

Despite 100% schema coverage, this tool has 17 parameters, no output schema, and no description of response format or typical usage patterns. The terse description leaves an agent guessing about whether the handle parameter is sufficient, how multiple matches are handled, and what to do with offset/limit/pageSize parameters that are said to be 'Ignored if this tool does not support it.'

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 description coverage is 100%, so the baseline is 3. The tool description itself adds no parameter-level meaning; it only restates the overall purpose naturally. The schema's 'Alias for `handle`. Prefer `handle`.' notes are the only parameter guidance, and those live in the schema, not the description.

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?

States a specific verb ('Resolve'), the input resource ('a LinkedIn handle'), and the output ('person entity id'), which clearly differentiates it from organization-resolve and other LinkedIn tools. The phrase 'person entity id' narrows the scope and leaves no ambiguity about what the tool does.

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 is given on when to use this tool vs alternatives like linkedin_live_people_search_v2 or linkedin_live_profile_get_v2. The description is purely definitional and provides no exclusions, prerequisites, or context about typical resolution workflows.

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

All Social Fetch tools Inspect

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.

Resolve LinkedIn person

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources