# io.github.linkedmash/linkedmash (remote · mcp.linkedmash.com) LinkedIn saved posts MCP server: search saves, draft, schedule, publish, and analyze content. - Trust score: 67/100 (medium) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `mcp.linkedmash.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp.md), [page](https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp) ## Channel facts - Endpoint: `https://mcp.linkedmash.com/api/mcp` - Transports: `streamable-http` - Auth: `required` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 63/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 40 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 62/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 8683 tokens (~217/item across 40 items; 40 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http linkedmash-linkedmash https://mcp.linkedmash.com/api/mcp ``` ### Codex ```toml [mcp_servers.linkedmash-linkedmash] url = "https://mcp.linkedmash.com/api/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "linkedmash-linkedmash": { "type": "remote", "url": "https://mcp.linkedmash.com/api/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add linkedmash-linkedmash --url https://mcp.linkedmash.com/api/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: linkedmash-linkedmash: url: "https://mcp.linkedmash.com/api/mcp" ``` ### Other ```json { "mcpServers": { "linkedmash-linkedmash": { "type": "http", "url": "https://mcp.linkedmash.com/api/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-03 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-01 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 65, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 64, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-28 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-27 (score 62, +1) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 61) First indexed and scored. ## MCP tools (40) ### `search_docs` (~245 tokens) Answer a question about Linkedmash THE PRODUCT — its features and how to reach them, how to change a setting, and pricing/billing. Use this for questions like 'where do I manage my subscription', 'how do I schedule a post', 'how much is the Creator plan', 'how do I change Lina's writing rules', 'how do I import my LinkedIn saves', 'what does Smart Folders do'. It returns the most relevant sections of the Linkedmash help guide — answer the user in your own words from them and point them to the exact page (e.g. Settings → Billing). For live prices, direct the user to the pricing page (/pricing). This tool reads product documentation only, NOT the user's saved posts or account data. Input parameters: - `query` (string): What the user wants to know about Linkedmash itself — a feature and how to reach it, a setting to change, or pricing/billing (e.g. 'where do I manage my subscription', 'how do I schedule a post', 'ho… ### `list_bookmarks` (~541 tokens) List bookmarks with optional filtering and pagination. Defaults: read AND unread bookmarks are both included (set is_unread_only=true only if the user asks for unread); archived bookmarks are excluded (set hide_archived=false to include them). Only apply the filters the user actually asked for — do NOT add media_type, unread, or date filters unprompted. IMPORTANT: Use this tool (with the 'author' parameter) when the user asks to show posts by a specific author, find posts from someone, or filter by author name. The 'author' parameter supports fuzzy matching of author names. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `cursor` (string): Pagination cursor for next page - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `limit` (number): Number of bookmarks to retrieve (1-100) - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `sort_by` (string): Sort order for results - `tag` (string): Filter by tag ### `search_bookmarks` (~638 tokens) Search through a user's LinkedIn bookmarks using either keyword (text) search or semantic (meaning-based) search. Supports all list_bookmarks filters, full-text search via the q field, and semantic search via the vector_search_term field for natural language or topic-based queries. IMPORTANT: At least one of 'q', 'vector_search_term', or 'author' must be provided. If the user asks to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'), use the 'author' parameter instead of putting the author name in the 'q' field. Use 'q' for searching post content, not for filtering by author. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `cursor` (string): Pagination cursor for next page - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `limit` (number): Number of bookmarks to retrieve (1-100) - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `q` (string): Keyword or text search query for finding bookmarks by exact words or phrases in post content. Do NOT use this for author names - use the 'author' parameter instead. - `sort_by` (string): Sort order for results - `tag` (string): Filter by tag - `vector_search_term` (string): Semantic search query for retrieving bookmarks based on meaning and context, not just keywords. Use for natural language questions or topic-based searches. ### `get_bookmark_count` (~472 tokens) Get the count of bookmarks matching the given filters. Supports the SAME filters as list_bookmarks (dates, author, tag, media_type, unread, q, comment) and the count respects all of them, so it is always consistent with a list_bookmarks call using identical filters. Defaults match list_bookmarks: read + unread included, archived excluded. The result echoes applied_filters — check it matches what the user asked before reporting the number. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `tag` (string): Filter by tag ### `list_labels` (~15 tokens) List all user's labels/tags ### `add_labels` (~200 tokens) Add a label to a FEW explicitly chosen posts (specific post_ids the user picked or is looking at). Either label_id or label_name must be provided. NEVER use this to label 'all posts matching a filter' (a date range, an author, a tag, unread…) — fetched lists are ONE PAGE, so labeling their ids silently misses the rest; use tag_bookmarks_by_filter instead, which labels EVERY match server-side in one call and returns matched/tagged counts. Input parameters: - `label_id` (string): ID of the existing label to add (use either label_id or label_name) - `label_name` (string): Name of the label to add (will create if doesn't exist, use either label_id or label_name) - `post_ids` (array, required): Specific post IDs to label — a small, explicitly chosen set. For 'all posts matching a filter' use tag_bookmarks_by_filter instead (paginated ids cover only one page). ### `remove_labels` (~84 tokens) Remove labels from bookmarked posts. Either label_id or label_name must be provided. Input parameters: - `label_id` (string): ID of the label to remove (use either label_id or label_name) - `label_name` (string): Name of the label to remove (use either label_id or label_name) - `post_ids` (array, required): Array of post IDs to remove labels from ### `tag_bookmarks_by_filter` (~686 tokens) Add a label to ALL bookmarks matching a filter in ONE server-side call. Use this — NOT list_bookmarks/search_bookmarks followed by add_labels — whenever the user asks to tag/label many posts by date range, author, tag, media type, or unread status (e.g. 'tag all posts older than March 2026 as Archive', 'label everything from John Doe as Hiring'). Date targeting: 'older than'/'before' DATE -> posted_to (or bookmarked_to); 'since'/'after' DATE -> posted_from (or bookmarked_from); use posted_* for when the post was published and bookmarked_* for when the user saved it; dates are ISO (YYYY-MM-DD). Provide label_name (created if it doesn't exist) or label_id. The tool returns matched/tagged/failed counts: ALWAYS tell the user how many posts were tagged; if 'truncated' is true, tell them it stopped at the cap and to narrow the date range to tag the rest; if 'failed' > 0, mention it. Never paginate or loop add_labels for bulk tagging — this one call handles the whole set. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `label_id` (string): ID of the existing label to add (use either label_id or label_name) - `label_name` (string): Name of the label to add — created if it doesn't exist (use either label_id or label_name) - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `q` (string): Optional keyword/text filter on post content to further narrow which posts get tagged. - `tag` (string): Filter by tag ### `remove_labels_by_filter` (~581 tokens) REMOVE a label from ALL bookmarks matching a filter in ONE server-side call — the mirror of tag_bookmarks_by_filter. Use this — NOT list/search + remove_labels on page ids — whenever the user asks to remove/clear a label from many posts by date range, author, tag, media type, or unread status (even phrased as 'fetch all X and remove the label'). Provide label_name or label_id; matching is automatically scoped to posts that carry the label. Returns matched/removed/failed counts: ALWAYS report them ('Removed from X of Y matching posts'); if 'truncated' is true, say it stopped at the cap. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `label_id` (string): ID of the label to remove (use either label_id or label_name) - `label_name` (string): Name of the label to remove (use either label_id or label_name) - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `q` (string): Optional keyword/text filter on post content to further narrow which posts get the label removed. - `tag` (string): Filter by tag ### `archive_bookmarks_by_filter` (~553 tokens) ARCHIVE all bookmarks matching a filter in ONE server-side call (reversible — archived posts stay recoverable in the app's Archive). Use for 'archive all posts ' style requests, even phrased as 'fetch then archive'. BEFORE calling: tell the user what will be archived (use get_bookmark_count with the same filter) and get an explicit yes — then call with confirm=true. Returns matched/affected counts: ALWAYS report them; if 'truncated' is true, say it stopped at the cap. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `confirm`: MUST be true, and ONLY after the user explicitly confirmed this destructive action in THIS conversation (you told them what will be affected and they said yes). Never set it on your own initiative. - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `q` (string): Optional keyword/text filter on post content to further narrow which posts are affected. - `tag` (string): Filter by tag ### `delete_bookmarks_by_filter` (~563 tokens) DELETE all bookmarks matching a filter in ONE server-side call. Deletion is soft (recoverable from the app for a while) but MUST be treated as destructive: BEFORE calling, tell the user exactly what will be deleted (use get_bookmark_count with the same filter to state the number) and get an explicit yes in this conversation — only then call with confirm=true. NEVER delete on your own initiative. Returns matched/affected counts: ALWAYS report them; if 'truncated' is true, say it stopped at the cap and offer to run again with a narrower filter. Input parameters: - `author` (string): Filter by author name or ID. Use this parameter when the user wants to find posts by a specific author (e.g., 'Show posts by John Doe', 'Find posts from Suresh sambantham'). Supports fuzzy matching -… - `bookmarked_from` (string): Filter by bookmark date range (ISO date string) - `bookmarked_to` (string): Filter by bookmark date range (ISO date string) - `comment` (string): Filter by comment: 'only' returns just saved comments, 'exclude' returns only top-level posts. If the user didn't ask about saved comments, prefer 'none' (or omit) — 'none' applies no comment filter.… - `confirm`: MUST be true, and ONLY after the user explicitly confirmed this destructive action in THIS conversation (you told them what will be affected and they said yes). Never set it on your own initiative. - `hide_archived`: Hide archived bookmarks. Default true (archived excluded). Set false ONLY when the user explicitly asks to include archived posts — do not fill this in otherwise. - `is_unread_only` (boolean): Filter to ONLY unread bookmarks. OMIT unless the user explicitly asks for unread posts. Default false: read AND unread bookmarks are both included. - `media_type` (string): Optional media-attachment filter. Accepted values: 'none', 'image', 'video', 'pdf'. When the user did NOT explicitly name a kind of media, pass 'none' (or omit the field) — 'none' means no media filt… - `posted_from` (string): Filter by post posting date range (ISO date string) - `posted_to` (string): Filter by post posting date range (ISO date string) - `q` (string): Optional keyword/text filter on post content to further narrow which posts are affected. - `tag` (string): Filter by tag ### `setup_vector_store` (~162 tokens) Initialize the vector store for semantic search. CRITICAL: When vector/semantic search fails with 'Vector Store Not Setup' error and you offered the user options to either initialize or use keyword search, and the user responds with 'first', 'option 1', 'yes', 'initialize', 'set it up', 'init', 'setup', 'go ahead' or similar confirmation, you MUST immediately call this tool. ALWAYS check your previous message in the chat history to confirm the user is responding to your options. Do NOT re-run the search tool - just call this tool. After calling this tool, inform the user that setup has started and may take a few minutes. This is an async operation that may take a few minutes to complete for large bookmark collections. ### `get_bookmark` (~68 tokens) Get a single saved LinkedIn post (bookmark) by its post_id — full content, author, media and tags. Use this to read one specific saved post, e.g. before creating content based on it. Input parameters: - `id` (string, required): The post_id of the saved bookmark to fetch ### `list_drafts` (~81 tokens) List the user's Content Studio posts (drafts, scheduled and published LinkedIn posts they are authoring). Optionally filter by status. Requires a paid Creator/Lifetime plan. Input parameters: - `status` (string): Filter content posts by status. If the user didn't name a status, prefer 'none' (or omit) — 'none' lists all of them. ### `create_draft` (~231 tokens) Create a new LinkedIn post draft in the user's Content Studio. Put the post body text in 'content'. Returns the created draft (with its id) which can later be scheduled or published. Requires a paid Creator/Lifetime plan. Input parameters: - `content` (string, required): The body text of the LinkedIn post/draft - `format` (string): Post format. OMIT (or pass 'none') unless the user asked for a specific format — default is text. - `media_mime_type` (string): MIME type of the attached media, e.g. image/png, video/mp4, application/pdf - `media_url` (string): Public URL of an image/video/PDF to attach (host one with upload_media). Set post_type to match. - `media_urls` (array): Optional array of media URLs to attach - `post_type` (string): Attachment type — set to image/video/pdf ONLY when actually attaching media (it drives how the post publishes to LinkedIn). No media attached -> prefer 'none' or omit. - `title` (string): Optional internal title for the draft ### `get_draft` (~44 tokens) Get a single Content Studio post/draft by its id. Requires a paid Creator/Lifetime plan. Input parameters: - `id` (string, required): The id of the content post/draft ### `update_draft` (~137 tokens) Update a Content Studio draft by id (partial — provide only the fields to change; 'content' is required for non-trash updates). Requires a paid Creator/Lifetime plan. Input parameters: - `content` (string): Updated body text (required for non-trash updates) - `format` (string): Updated post format. OMIT (or pass 'none') unless the user asked to change it. - `id` (string, required): The id of the content post/draft to update - `media_mime_type` (string): Updated media MIME type - `media_urls` (array): Updated media URLs - `title` (string): Updated internal title ### `delete_draft` (~46 tokens) Delete (move to trash) a Content Studio draft by its id. Requires a paid Creator/Lifetime plan. Input parameters: - `id` (string, required): The id of the content post/draft ### `upload_media` (~186 tokens) Host an image, video, or PDF and get back a public URL to attach to a post (use the returned url as media_url, with the matching post_type). Provide a remote 'url' to re-host (recommended — the asset then stays available until a scheduled publish), or 'file_base64' (+ file_name) for raw bytes. Requires a paid Creator/Lifetime plan. Input parameters: - `file_base64` (string): Base64-encoded file bytes (alternative to url; best for smaller files) - `file_name` (string): File name, e.g. 'chart.png' (required when using file_base64) - `mime_type` (string): MIME type, e.g. image/png, video/mp4, application/pdf - `url` (string): Public http(s) URL of the media to host (recommended — it then stays available until a scheduled publish) ### `schedule_post` (~207 tokens) Schedule a Content Studio draft to publish to LinkedIn, or publish it immediately. Set publish_at to 'now' (publish right away), 'next-slot' (the next free slot in the user's posting schedule), or an ISO-8601 timestamp. A timezone (IANA, e.g. 'America/New_York') is required unless publish_at is 'now'. Requires a paid Creator/Lifetime plan. Input parameters: - `id` (string, required): The id of the draft to schedule or publish - `media_mime_type` (string): Optional media MIME type - `media_url` (string): Optional media URL to attach - `post_type` (string): Post type (default: text) - `publish_at` (string, required): When to publish: 'now', 'next-slot' (next free posting slot), or an ISO-8601 timestamp - `timezone` (string): IANA timezone, e.g. 'America/New_York'. Required unless publish_at is 'now'. ### `get_queue` (~90 tokens) List the user's posting queue — scheduled and published LinkedIn posts, grouped by date. Optionally filter by status. Each entry includes its schedule id (use it to cancel/reschedule). Requires a paid Creator/Lifetime plan. Input parameters: - `status` (string): Filter the queue by status. If the user didn't name a status, prefer 'none' (or omit) — 'none' returns the whole queue. ### `get_posting_slots` (~73 tokens) Get the next free posting slots from the user's recurring posting schedule (in their timezone). Use a returned slot's timestamp as publish_at when scheduling. Requires a paid Creator/Lifetime plan. Input parameters: - `count` (number): How many free slots to return - `timezone` (string): IANA timezone for the slots ### `cancel_scheduled_post` (~52 tokens) Cancel a scheduled post by its schedule id (from a get_queue entry). Requires a paid Creator/Lifetime plan. Input parameters: - `schedule_id` (string, required): The id of the scheduled post (from the queue entries) ### `get_posting_schedule` (~40 tokens) Get the user's recurring posting schedule — the weekly time-slot grid and timezone that drive 'next-slot' scheduling. Requires a paid Creator/Lifetime plan. ### `set_posting_schedule` (~97 tokens) Replace the user's recurring posting schedule (weekly time-slot grid + timezone). 'grid' is an array of slots like { time: '8:30 am', days: { Mon: true, Wed: true } }. These slots drive 'next-slot' scheduling. Requires a paid Creator/Lifetime plan. Input parameters: - `grid` (array, required): Recurring posting slots - `timezone` (string, required): IANA timezone for the recurring posting schedule ### `get_analytics` (~92 tokens) Get the user's account-level LinkedIn analytics — impressions, reactions, comments, reshares, members reached and follower growth — over a time window (date_range like '7d', '30d', '90d'). Requires a paid Creator/Lifetime plan. Input parameters: - `date_range` (string): Time window, e.g. '7d', '30d', '90d' (default 30d) ### `get_post_analytics` (~94 tokens) Get per-post LinkedIn analytics for the user's recently published posts (impressions, engagements, likes, comments, etc.) over a time window. Requires a paid Creator/Lifetime plan. Input parameters: - `date_range` (string): Time window, e.g. '7d', '30d', '90d' (default 30d) - `limit` (number): Max number of recently-published posts to return ### `get_growth_digest` (~97 tokens) Get the user's GROWTH DIGEST — their positioning, content pillars, authority gaps, ranked what-to-do-next actions (with ready-to-use draft prompts), and this week's numbers (new saves, posts published). USE THIS whenever the user asks what they should post/do next, wants a growth plan or weekly review, or asks how to build authority — then walk them through the top next steps. Requires a paid Creator/Lifetime plan. ### `remember` (~392 tokens) Persist a DURABLE fact, preference, writing-style trait, or standing instruction about the user so it is remembered in FUTURE conversations (not just this one). Use this when the user states a lasting preference or instruction (e.g. 'always keep replies short', 'I write for early-stage founders', 'my timezone is IST', 'use a punchy tone'). kind = preference|style|fact|instruction; key = a short stable slug (reusing a key overwrites it); value = a concise phrase. Do NOT store secrets, passwords, tokens, payment details, or sensitive personal data. Optional mode: 'append' grows an existing note instead of overwriting. If a write is REFUSED (e.g. it would overwrite something the user set themselves, which takes precedence), you'll get an error explaining why — tell the user rather than retrying. Input parameters: - `key` (string, required): Short stable slug identifying this memory within its kind (e.g. 'tone', 'audience', 'timezone', 'response_length'). Re-using the same key overwrites the previous value. - `kind` (string, required): What kind of durable memory this is. 'preference' = how the user likes things done; 'style' = the user's writing voice (tone/structure/audience/formats/signature phrases); 'fact' = a stable fact abou… - `mode` (string): How to write when this (kind, key) already exists: 'overwrite' (default) replaces the value; 'append' adds it on a new line. OMIT (or pass 'none') for the default — only use 'append' to grow an accum… - `value` (string, required): The memory content — a concise phrase (keep it under ~160 characters). ### `recall` (~99 tokens) Retrieve what you durably remember about the user (preferences, writing voice/style, facts, standing instructions) across conversations. Optionally pass a free-text 'query' to narrow the results; omit it to get the full memory digest. Use this when you need to recall the user's preferences or voice before answering or drafting. Input parameters: - `query` (string): Optional free-text filter to narrow which remembered items to return. Omit to return the user's full memory digest. ### `forget` (~124 tokens) Delete a durable user memory by its 'key' (optionally scoped to a 'kind'). Use this when the user asks you to forget something you remembered about them, or to correct an outdated preference/fact before re-adding it with remember. Input parameters: - `key` (string, required): The slug (key) of the memory to delete. Removes every memory with that key for the user. - `kind` (string): Optional: restrict deletion to this kind only. Prefer 'none' (or omit) unless the user named a kind — 'none' removes every kind sharing the key. ### `list_smart_folders` (~77 tokens) List the user's smart folders (a.k.a. filtered views / triage views). A smart folder is a saved filter/workflow over their saved posts, optionally split into tabs (triage buckets/stages). Returns each folder's slug (use it with the other smart-folder tools), name, description, filter query and tabs. ### `get_smart_folder` (~84 tokens) Get one smart folder (filtered view) by its slug — its name, description, filter query (base_query) and tabs (triage buckets). Use list_smart_folders first to find the slug. To read the posts inside, use get_smart_folder_posts. Input parameters: - `slug` (string, required): The smart folder's slug (from list_smart_folders). ### `get_smart_folder_posts` (~157 tokens) List the saved LinkedIn posts inside a smart folder (filtered view). Pass the folder's slug (from list_smart_folders). Optionally pass 'bucket' to return only one tab/stage (triage bucket) of the folder; omit it for all posts in the folder. Paginate with 'cursor' (a numeric offset) and 'limit'. Input parameters: - `bucket` (string): Tab/stage name within the folder (a triage bucket); omit for all posts in the folder. - `cursor` (number): Numeric offset for pagination. - `limit` (number): Number of posts to retrieve (1-100). - `slug` (string, required): The smart folder's slug (from list_smart_folders). ### `create_smart_folder` (~124 tokens) Create a smart folder (filtered view) — a saved filter/workflow over the user's saved posts. 'name' is required; 'base_query' is the filter query that defines which posts belong; 'triage_buckets' are optional tabs/stages inside the folder. Returns the created folder (with its slug). Input parameters: - `base_query` (string): The folder's filter query. - `description` (string): Optional description of the folder. - `name` (string, required): Folder name. - `triage_buckets` (array): Tabs/stages inside the folder. ### `update_smart_folder` (~135 tokens) Update a smart folder (filtered view) by its slug. Provide only the fields to change: 'name', 'description', 'base_query' (the filter query), and/or 'triage_buckets' (the tabs/stages). Use list_smart_folders to find the slug. Input parameters: - `base_query` (string): Updated filter query. - `description` (string): Updated description. - `name` (string): Updated folder name. - `slug` (string, required): The smart folder's slug (from list_smart_folders). - `triage_buckets` (array): Updated tabs/stages inside the folder. ### `delete_smart_folder` (~69 tokens) Delete a smart folder (filtered view) by its slug. This removes the saved filter/workflow itself — it does NOT delete any saved posts. Use list_smart_folders to find the slug. Input parameters: - `slug` (string, required): The smart folder's slug (from list_smart_folders). ### `trigger_pdf_export` (~371 tokens) Start exporting the user's saved LinkedIn posts to PDF. Use this when the user asks to export/download/back up their saved posts as a PDF (e.g. 'export all my saved posts to PDF', 'give me a PDF of my saved AI posts'). By default it exports the WHOLE library; to scope it, pass post_ids for a specific selection, or a filter (search_query for a keyword, filter+value e.g. author/label/type, tags, or author). This kicks off an async job — it does NOT return the file. ALWAYS tell the user the export has started and to open the Export Center link (returned in the message) to view and download it once ready; large exports can take up to a minute. Input parameters: - `author` (string): Restrict the export to a specific author (name or id). Shorthand for filter='author'. - `filter` (string): Filter dimension to scope the export, paired with 'value' (e.g. 'author' + an author id, 'label' + a tag, 'type' + image/video/pdf). If the user asked to export everything, prefer 'none' (or omit) —… - `post_ids` (array): Specific saved-post ids to export. Omit to export by filter or the whole library. - `search_query` (string): Keyword/text query to scope which saved posts are exported (matches post content). OMIT unless the user asked to export a subset. - `tags` (array): Restrict the export to saved posts carrying these tags/labels. OMIT unless the user named tags. - `value` (string): The value for 'filter' (e.g. the author id, the tag/label, or the media type). ### `trigger_csv_export` (~339 tokens) Start exporting the user's saved LinkedIn posts to a CSV (spreadsheet) file. Use this when the user asks to export/download their saved posts as CSV or to a spreadsheet. By default it exports the WHOLE library; to scope it, pass post_ids for a specific selection, or a filter (search_query, filter+value e.g. author/label/type, tags, or author). This records the export — it does NOT return the file. ALWAYS tell the user the export has started and to open the Export Center link (returned in the message) to view and download it. Input parameters: - `author` (string): Restrict the export to a specific author (name or id). Shorthand for filter='author'. - `filter` (string): Filter dimension to scope the export, paired with 'value' (e.g. 'author' + an author id, 'label' + a tag, 'type' + image/video/pdf). If the user asked to export everything, prefer 'none' (or omit) —… - `post_ids` (array): Specific saved-post ids to export. Omit to export by filter or the whole library. - `search_query` (string): Keyword/text query to scope which saved posts are exported (matches post content). OMIT unless the user asked to export a subset. - `tags` (array): Restrict the export to saved posts carrying these tags/labels. OMIT unless the user named tags. - `value` (string): The value for 'filter' (e.g. the author id, the tag/label, or the media type). ### `trigger_json_export` (~337 tokens) Start exporting the user's saved LinkedIn posts to a JSON file (a structured backup). Use this when the user asks to export/download/back up their saved posts as JSON. By default it exports the WHOLE library; to scope it, pass post_ids for a specific selection, or a filter (search_query, filter+value e.g. author/label/type, tags, or author). This records the export — it does NOT return the file. ALWAYS tell the user the export has started and to open the Export Center link (returned in the message) to view and download it. Input parameters: - `author` (string): Restrict the export to a specific author (name or id). Shorthand for filter='author'. - `filter` (string): Filter dimension to scope the export, paired with 'value' (e.g. 'author' + an author id, 'label' + a tag, 'type' + image/video/pdf). If the user asked to export everything, prefer 'none' (or omit) —… - `post_ids` (array): Specific saved-post ids to export. Omit to export by filter or the whole library. - `search_query` (string): Keyword/text query to scope which saved posts are exported (matches post content). OMIT unless the user asked to export a subset. - `tags` (array): Restrict the export to saved posts carrying these tags/labels. OMIT unless the user named tags. - `value` (string): The value for 'filter' (e.g. the author id, the tag/label, or the media type). ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp#diagnostics ## Score history - 2026-08-03: 67 - 2026-08-02: 66 - 2026-08-01: 66 - 2026-07-31: 65 - 2026-07-30: 64 - 2026-07-29: 63 - 2026-07-28: 63 - 2026-07-27: 62 - 2026-07-26: 61 ## Links - Remote endpoint: https://mcp.linkedmash.com/api/mcp - Authorisation metadata: https://mcp.linkedmash.com/.well-known/oauth-protected-resource/api/mcp - Website: https://www.linkedmash.com/for-ai-agents - Changelog RSS feed: https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp/changelog.json - HTML version of this page: https://verifymcp.io/servers/linkedmash-linkedmash/api-mcp