Skip to main content
Glama
negrueu

linkedin-company-admin-mcp

by negrueu

Reshare company post on personal profile

personal_reshare_company_post

Reshare a Company Page post to your personal profile for employee advocacy, expanding your organization's reach on LinkedIn.

Instructions

Share a Company Page post onto the signed-in user's profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thoughts_textNoOptional commentary added above the reshared post.
source_post_urnYesURN of the company post (from ``company_list_posts``).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already indicate readOnlyHint=false, correctly aligning with the 'Share' action. The description adds that the share goes to the personal profile, but does not disclose potential side effects like visibility or permission requirements. With annotations covering the safety profile, this level of detail is acceptable.

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?

The description is a single, focused sentence with no redundant information. It efficiently communicates the core purpose.

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

Completeness5/5

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

The tool is simple with only 2 parameters, full schema coverage, and an output schema present. The description, combined with the structured fields, provides complete context for correct invocation.

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%, with source_post_urn clearly described as coming from company_list_posts and thoughts_text as optional commentary. The description itself adds no parameter details, so baseline 3 is appropriate.

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?

The description clearly states the action 'Share a Company Page post onto the signed-in user's profile', specifying both the resource (company post) and the destination (personal profile). This distinguishes it from the sibling 'company_reshare_post' which targets the company page.

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?

The description conveys the context of use by specifying 'onto the signed-in user's profile', which implies a distinction from company-level resharing. However, it does not explicitly name alternatives or provide when-not-to-use guidance, so it falls short of a 5.

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/negrueu/linkedin-company-admin-mcp'

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