emilianooliveira
08/12/2025, 11:21 PMComposio Support Agent
08/13/2025, 6:06 AMLINKEDIN_GET_MY_INFO Tool.emilianooliveira
08/13/2025, 1:43 PMemilianooliveira
08/13/2025, 1:43 PMurn:li:person:wkvedKSlFXemilianooliveira
08/13/2025, 1:44 PMComposio Support Agent
08/13/2025, 2:10 PMurn:li:person:wkvedKSlFX was used for the previous Tool call which led to the error? you can click on view payload and check the urn used. I've attached an image for your ref:
https://cdn.discordapp.com/attachments/1404968047172784359/1405191722140438649/Screenshot_2025-08-13_at_19.38.30.png?ex=689dee45&is=689c9cc5&hm=2693f453561b678e5d4bd0601b8ef7ba309b11105dae40eb0604b9eda5979a6f&emilianooliveira
08/14/2025, 12:15 AMjson
{
"author": "urn:li:person:123456789",
"commentary": "...",
"distribution": {
"feedDistribution": "MAIN_FEED"
},
"lifecycleState": "PUBLISHED",
"visibility": "PUBLIC"
}
@udaysidagana here is an example of a payload that resulted in a forbidden error.emilianooliveira
08/14/2025, 12:17 AMabhishekpatil4
08/14/2025, 8:07 AMemilianooliveira
08/15/2025, 12:22 AMemilianooliveira
08/15/2025, 12:22 AMemilianooliveira
08/15/2025, 12:22 AMabhishekpatil4
08/15/2025, 6:05 AMemilianooliveira
08/15/2025, 10:42 PMemilianooliveira
08/15/2025, 10:44 PMabhishekpatil4
08/16/2025, 5:46 AMemilianooliveira
08/19/2025, 8:11 PMemilianooliveira
08/19/2025, 8:12 PMemilianooliveira
08/19/2025, 8:27 PMabhishekpatil4
08/20/2025, 12:25 PMurn:li:person:wkvedKSlFXemilianooliveira
08/20/2025, 7:17 PMurn:li:person:wkvedKSlFX have resulted in the an error in the quick search I have made.
There is no filter options and a quick cmf + f with manual pagination has shown no recent errors.
@User Can you base your investigation in one of the other 5 exemplars I just sent?abhishekpatil4
08/21/2025, 7:56 AMurn:li:person:wkvedKSlFX its a successful tool call because its the correct value, in case of other examples shared by you, they are incorret values. For example in the first one 'urn: li:person:123456789 is incorrect and won't work.emilianooliveira
08/21/2025, 2:31 PMemilianooliveira
08/21/2025, 2:31 PMemilianooliveira
08/21/2025, 2:32 PMemilianooliveira
08/21/2025, 2:34 PMabhishekpatil4
08/22/2025, 6:56 AMLINKEDIN_GET_MY_INFO which is urn:li:person:wkvedKSlFX.emilianooliveira
08/22/2025, 3:46 PMemilianooliveira
08/22/2025, 4:02 PMemilianooliveira
08/22/2025, 5:36 PMemilianooliveira
08/22/2025, 6:36 PMLINKEDIN_CREATE_LINKED_IN_POST is requiring the configuration of the LINKEDIN_GET_MY_INFO, which is completely unnecessary and problematic since the agent a lot of times do not make the decision of calling the get my info beforehand.
In the post creation tool the correct path is to get the author before calling the post creation. No reason for it to not be the case.
https://cdn.discordapp.com/attachments/1404968047172784359/1408520250139349013/image.png?ex=68aa0a34&is=68a8b8b4&hm=ac7b40be6dc75885853d94cabc986111e4e6659987e286b65c353e76c9f2e4f0&emilianooliveira
08/22/2025, 6:36 PMemilianooliveira
08/23/2025, 12:08 AMabhishekpatil4
08/25/2025, 4:43 AMemilianooliveira
08/25/2025, 10:40 PMget my info before calling create linked in post. This is definitively not something that I should be required to do.
Tools should be independent from each other, specially regarding authorization.emilianooliveira
08/25/2025, 10:41 PMabhishekpatil4
08/26/2025, 3:06 PMLINKEDIN_GET_MY_INFO and pass it to LINKEDIN_CREATE_LINKED_IN_POST because if the post is being made by an organization/company, the value needs to come from LINKEDIN_GET_COMPANY_INFO instead. This needs to be handled on the user's end.emilianooliveira
08/27/2025, 1:54 PMurn?
Just so you know, the MCP right now is extremely unreliable. Maybe because of the examples attribute that is meant to help, but is actually generating hallucinations.