AIGigLab MCP Server

set_linkedin_post_target

Choose whether to post to a personal LinkedIn profile or a specific company page by providing the target type and optional company details.

Instructions

Set whether to post to the 'personal' profile or a specific 'company' page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postTarget": "<postTarget>"
    },
    "name": "set_linkedin_post_target"
  }
}

Input Schema

Name	Required	Description
`logo`	No	Company logo URL
`name`	No	Company name
`orgId`	No	Required if postTarget is 'company'
`postTarget`	Yes	The target type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Jul 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states the action but not side effects, state changes, permissions, or error conditions (e.g., what if orgId missing when postTarget is company).

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?

Single sentence, no wasted words. Front-loaded with the core purpose. Appropriate length for the tool's complexity.

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

Completeness2/5

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

Tool has 4 parameters but no output schema and no annotations. Description lacks details on parameter dependencies, return value, or side effects. Incomplete for safe autonomous use.

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 coverage is 100%, so baseline is 3. Description adds no additional meaning beyond the schema's parameter descriptions. It does not explain relationships between parameters (e.g., orgId conditional on postTarget).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: setting whether to post to personal profile or a company page. It is specific and distinguishes from siblings like trigger_linkedin_post_now. However, it doesn't elaborate on what 'set' means operationally.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It doesn't indicate if it's a prerequisite for posting or how it relates to other LinkedIn tools like update_linkedin_config or trigger_linkedin_post_now.

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