https://linen.dev logo
LinkedIn Post Creation Issue
# 🖥│support-forum
e
The create post tool from the LinkedIn toolkit keep returning the forbidden error, which is making us reluctant to adopting Composio as our main MCP partner. In some accounts it's intermittent, in others it is constant and in others it requires the user to recreate the connection. Are you guys aware of that? If so, what are you doing to circumvent the issue? https://cdn.discordapp.com/attachments/1404968047172784359/1404968047411728475/Screenshot_2025-08-12_at_20.14.25.png?ex=689d1df5&is=689bcc75&hm=29a4d5851c9051786be5c81c4a6b962818cc45c75a6a7bcd7e215f88335e0edb&
c
Hi Emiliano, Could you recheck the Author URN? You can find it by using
LINKEDIN_GET_MY_INFO
Tool.
urn:li:person:wkvedKSlFX
I have not checked if there are issues at the moment, but I've had in the past with this account.
c
Can you check if
urn: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&
e
Copy code
json
{
    "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.
Does that satisfy the requirements to start the investigation? Next week we'll be starting our platform tests with focus group what would me crucial to have this feature resolved.
a
Hey @emilianooliveira, Looks like you're still passing an invalid urn, can you try passing [this](https://discord.com/channels/1170785031560646836/1404968047172784359/1405185039720779807) and lmk if that worked for you? If issue persist please share the logId.
e
Sorry. Here is a collection of logs with the forbidden error: - log_T2r-hVUOqAjf - log_LpA1sLJ0AHnm - log_M01iF0HYlEl3 - log_dyy3dh4Yrk-w - log_-enEx9s84Y8Q - log_ymTZlJplTEYx
Is it enough to investigate?
@abhishekpatil4 👆
e
Guys, please. If you have the log id you have everything you need to investigate. We’re on the verge of releasing our solution and we’d love to be partners with you guys, but I’ve given you multiple instances of the issue we’re facing already. Could you please investigate?
Posting on LinkedIn is one of the main features we need.
a
@emilianooliveira I understand your urgency. We can't access the payload for privacy reasons, which is why I'm asking for the payload screenshot. I'm here to help resolve this quickly - would you be able to share that screenshot, or would a quick call work better for you?
Anything else?
@udaysidagana ?
a
I don't think you're passing the correct URN, its [this](https://discord.com/channels/1170785031560646836/1404968047172784359/1405185039720779807) one. Can you pass that and retry? >
urn:li:person:wkvedKSlFX
e
None of the requests regarding
urn: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?
a
Yes, in case of
urn: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.
e
@abhishekpatil4 I dont get it... You mean It's LLM hallucination?
What about the other prints? They do not seem invalid like the one you've metioned.
Shouldn't this be a parameter automatically discovered through the connection the tool is being executed?
What do you recommend to circumvent the issue? This is not a parameter we pass programatically from our end.
a
Not sure, could be the LLM getting hallucinating // getting params from other tools, If you happen to have used tracing (LangSmith // OpenAI traces) would recommend troubleshooting that out and see how that value obtained. What I can say for sure is, if you want to create a post you need to pass YOUR author value which can be obtained from
LINKEDIN_GET_MY_INFO
which is
urn:li:person:wkvedKSlFX
.
e
I see. So the MCP needs some updating so it can become more reliable. Is that it? These errors occured with sonnet 4, which is the best tool caller at the moment.
I just don’t get why the discovery of this attribute is not built in the create post tool itself. Shouldn’t you guys internalize the issue with the engineers? From my end you are requiring me to develop a workaround for something that should simply work.
@abhishekpatil4 ?
This is a cursor debug snapshot. The way this is structured, the
LINKEDIN_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&
Could you reach the engineering team to check if this will be done?
a
Not an issue with the MCP, fine tuning the prompt should solve this.
e
Currently I am solving the issue by performing a call on my end to
get 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.
Can you mention someone from the product team in the thread? I am pretty confident this is a bug.
a
This isn't a bug—it's how LinkedIn's API works. We can't dynamically get the author value via
LINKEDIN_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.
e
@abhishekpatil4 now I get it. But can't you simply check if the connection belongs to an organization or a person and get the
urn
? 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.