const result = await getComposioClient().tools.execute(
    'LINKEDIN_GET_MY_INFO',
    {
      userId: '',
      connectedAccountId: '',
      arguments: {},
      version: 'latest',
      dangerouslySkipVersionCheck: true,
    },
  );

this is providing only

{
  "data": {
    "id": "",
    "localizedFirstName": "",
    "localizedLastName": "",
    "profilePicture": {
      "displayImage": ""
    }
  },
  "error": null,
  "successful": true,
  "logId": "log_yaSh4-7PqLNn"
}

(All strings removed for privacy) THe documentation here https://dashboard.composio.dev/deepaksangleok_workspace/deepaksangleok_workspace_first_project/toolkits/linkedin says it provides a lot more info like headline, linkedin slug (vanity name), etc.

Hi there, Thanks for the detail, that makes it easy to pin down. What you're seeing is expected with the standard LinkedIn connection, not a bug in your call. The extra fields the toolkit page lists (headline, vanity name/slug, maiden name, etc.) require an elevated LinkedIn permission,

r_basicprofile

. Our managed LinkedIn app doesn't hold that scope, so the request to LinkedIn's full profile endpoint falls back to their basic profile endpoint and returns just the

id

, first name, last name, and profile picture you got back. No reconnect or argument change will alter this. The catch is that LinkedIn has deprecated those profile-read scopes and only grants them to apps it has specifically approved as partners, so in practice those richer fields aren't reliably retrievable through the API today. You're right that the toolkit page over-promises here, and I'll get that field list looked at internally. If there's a specific field you're blocked on, let me know what you're building and I'll see if there's another action that can get it. Just reply here. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.

Ok thanks, that helps

quick follow-up on the LinkedIn profile fields issue: we shipped the enrichment fix for

LINKEDIN_GET_MY_INFO

. It now tries the member-profile API when the initial response is sparse and can return

headline

,

localizedHeadline

,

vanityName

, and a derived

profileUrl

when LinkedIn returns those fields for the app. If you retry and still only see lite fields, send a fresh log id and we’ll check whether LinkedIn is gating the fields for that connection.