Skip to main content
Glama

Save LinkedIn Post

save_post

[Acquire · 1 credit · writes] Save a LinkedIn post to your library by its URL. Resolves the post and stores it with source_type='saved'. Optionally pins the post into any collection you own (manual or smart — pinning into a smart collection adds it as an extra alongside the rule's matches). Costs 1 credit per call. Failed lookups don't charge.

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": {
      "url": "<url>"
    },
    "name": "save_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic LinkedIn post URL. Accepts linkedin.com/posts/... permalinks and linkedin.com/feed/update/urn:li:activity:... feed URLs.
collection_idNoOptional collection UUID to pin the post into. Must be a collection you own — any type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the credit cost (1 per call), the billing exception (failed lookups don't charge), the resolution/storage behavior, and the smart-collection side effect of adding an extra item alongside rule matches. These are exactly the operational facts an agent needs before committing a paid mutation; only the re-save/duplicate behavior implied by idempotentHint=false goes unaddressed.

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?

Front-loaded with a compact tag line, then dense sentences that each carry a distinct fact (resolution, storage, pinning semantics, cost, failure billing). The only redundancy is "Costs 1 credit per call" restating the "1 credit" already in the header, though it earns some of that back by adding the per-call and failure caveats.

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?

For a two-parameter paid write tool with annotations present and no output schema, the description covers cost, failure behavior, stored state, and the optional pinning side effect. It stops short of describing what the call returns or what happens when the same URL is saved twice, which are the remaining gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that collection_id pins the post into any owned collection and clarifies the manual-vs-smart collection consequence, which the schema does not. The url parameter's accepted formats are left entirely to the schema, which is acceptable given full coverage.

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?

States a specific verb+resource ("Save a LinkedIn post to your library") plus the mechanism ("by its URL"), and the bracket tag marks it as a write/acquire operation. This is clearly distinguishable from siblings like get_posts (retrieval) or add_to_collection (pure pinning), and the phrase "stores it with source_type='saved'" pins down the resulting state.

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?

Gives clear context for the optional second parameter: pinning is optional and available for any collection you own, with a note that smart collections behave differently. It does not explicitly say when to prefer this over add_to_collection or how it relates to feed/search tools, so the alternative-routing element is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources