Skip to main content
Glama
Upload-Post

Upload-Post

Official

Save a Pin or bookmark a post

save_post
Idempotent

Save an existing Pinterest Pin to a board or section, or bookmark a Bluesky post, with a preview and explicit approval before sending.

Instructions

Pinterest: save an existing Pin (post_id) to one of the profile's boards (pinterest_board_id, optionally a section); it shows on that board. Bluesky: bookmark a post (private). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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": {
      "platform": "<platform>",
      "user": "<user>",
      "post_id": "<post_id>"
    },
    "name": "save_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name.
post_idYesPinterest Pin id, or Bluesky at:// URI or bsky.app link.
platformYes
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
pinterest_board_idNoPinterest: the board to save to (required).
pinterest_board_section_idNoPinterest: a section of that board.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: nothing is sent without `confirmed`, the first call returns a preview, and the Bluesky bookmark is private while the Pinterest save is publicly visible on the board. It stops short of describing failure modes or rate limits.

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 the platform-specific action, then the approval protocol, with no filler sentences. It is dense but every clause carries information; the parenthetical asides are the only mild clutter.

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?

An output schema exists, so return values need not be explained, and the description covers both platform branches plus the confirmation gate. The remaining gap is what happens on an invalid board id or a failed save, which an agent would have to discover at call time.

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 83%, so the baseline is 3, but the description adds meaning the schema does not: `post_id` must be an *existing* Pin or a Bluesky at:// URI/bsky.app link, and `pinterest_board_id` is effectively required for Pinterest even though it is not in the required array. That resolves a real ambiguity an agent would otherwise hit.

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 and resource for each platform: saving an existing Pin to a board/section on Pinterest, and bookmarking a post on Bluesky. The two-platform split is explicit, so an agent can tell this apart from siblings like repost_post or approve_post without opening a schema.

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 a clear when-to-use rule per platform and a precise two-step protocol: call without `confirmed` for a preview, show the user, then repeat with `confirmed: true`. It does not name alternative tools (e.g. repost vs save) or state when not to use it, which keeps it 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.

Deploy Server

Other Tools