Skip to main content
Glama
himanshu31shr

LinkedIn MCP Server

upload_image

Upload an image to LinkedIn by providing a URL. Returns an image URN for including in LinkedIn posts. Optionally add alt text for accessibility.

Instructions

Upload an image to LinkedIn from a URL and get an image URN for use in posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageUrlYes
altTextNo
Behavior3/5

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

No annotations provided. Description states upload and return of URN but lacks details on permissions, error handling, size limits, or synchronous behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence front-loads purpose. Could be improved by briefly mentioning altText, but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but description usefully mentions returning an image URN. Missing constraints like accepted formats, but adequate for a simple upload tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% coverage. Description only mentions 'URL' (imageUrl) but ignores altText parameter entirely, leaving its meaning and constraints undocumented.

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?

Description clearly states verb 'upload', resource 'image', domain 'LinkedIn', and outcome 'get an image URN for use in posts'. Differentiates from sibling tools like create_image_post which creates a post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for uploading before creating image posts, but does not explicitly state when not to use or mention alternatives like direct file upload.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/himanshu31shr/linkedin-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server