Skip to main content
Glama

update_linkedin_config

Update LinkedIn automation configuration for topics, schedules, tone, and post types to tailor your content strategy.

Instructions

Update LinkedIn automation configuration (e.g., topics, schedules, tone, post types).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toneNoTone of voice
topicsNoCRITICAL: This replaces the ENTIRE topics list. To add a new topic without deleting existing ones, you MUST include all existing topics (including their _id) in this array alongside the new one.
isActiveNoEnable or disable the automation
timezoneNoTimezone for scheduling (e.g., 'Asia/Calcutta')
postTypesNoType of posts to generate
oneTimeDateNoDate-time string for one_time scheduling (e.g. '2026-07-08T16:40:00.000Z')
customPromptNoAdditional custom instructions for the AI
dailyScheduleNoCRITICAL: This replaces the ENTIRE daily schedule list. You MUST include all existing schedules you want to keep.
oneTimeTopicIdNoTopic ID for the one_time post
schedulingModeNoScheduling mode
targetAudienceNoTarget audience description (e.g., 'Software Engineers', 'Startup Founders')
weeklyScheduleNoWeekly schedule slots keyed by day e.g. { 'Wed': [{ time: '16:40' }] }
carouselImageCountNoNumber of images for carousel_post (min 2, max 5)
Behavior1/5

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

No annotations provided, so description carries full burden. The description fails to disclose that the tool replaces entire arrays (topics, dailySchedule) as noted in the schema but omitted from the tool description. This is a critical behavioral trait that should be surfaced.

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

Conciseness3/5

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

The description is a single concise sentence, but it sacrifices necessary detail. It is front-loaded but incomplete for a tool with 13 parameters and replacement semantics.

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

Completeness1/5

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

Given the high parameter count (13) with nested objects and critical replacement behaviors, the one-sentence description is severely inadequate. It does not explain return values, idempotency, or the destructive nature of array parameters.

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%, so baseline is 3. The tool description lists example parameter categories already covered in the schema, adding no additional meaning beyond what the schema provides.

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 it updates LinkedIn automation configuration with examples (topics, schedules, tone, post types). While it distinguishes from sibling tools like get_linkedin_config or trigger_linkedin_post_now, it does not explicitly differentiate from other update tools in the sibling list.

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 versus alternatives. It does not mention prerequisites, when not to use it, or suggest other tools for different scenarios.

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/JayIsDeveloper/aigiglab-mcp-server'

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