Skip to main content
Glama

Share a post with a client for approval

clipember_create_preview_link

Create a public preview link (no login) for one post group: the client sees the video, the caption and settings for each network and the time, can comment by name, and can Approve or Request changes. The URL is returned ONCE — give it to the user right away; creating a new link revokes the old one. By default it expires after 30 days, or a day after the group's last post if that is later (max 90). If the account has "publish only approved" on, the group's queued posts become drafts until the client approves.

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": {
      "groupId": "<groupId>"
    },
    "name": "clipember_create_preview_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesgroupId of the post (from clipember_create_post or clipember_list_scheduled_posts) — all its networks are shared together
expiresInDaysNoDays until the link stops working (default 30, or until a day after the last post)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing three non-obvious behaviors: the URL is returned only once and cannot be re-read, minting a new link revokes the previous one, and an account with 'publish only approved' will flip the group's queued posts to drafts. These are exactly the side-effect and irreversibility facts an agent needs before invoking a write tool.

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?

Purpose is front-loaded in the first clause, then the review mechanics, then the return/revocation warning, then expiry, then the approval side effect — a logical order. The clause enumerating everything the client sees is slightly padded but does real work in explaining what the link exposes. No filler sentences.

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

Completeness5/5

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

There is no output schema, and the description covers the return value ('The URL is returned ONCE'), the lifecycle of prior links, expiry defaults and ceilings, and downstream effects on scheduled posts. For a two-parameter mutation tool, an agent has everything needed to call it and to tell the user what to do with the result.

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 the baseline is 3. The description restates the expiry rule (default 30 days, until a day after the last post if later, max 90) which the schema already documents for expiresInDays, and adds nothing about groupId beyond what the schema says. No additional semantic value over the structured fields.

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 gives a precise verb and resource: 'Create a public preview link (no login) for one post group,' and even enumerates what the client sees (video, caption, per-network settings, time, comments, approve/request-changes). That is far more specific than a tautology. It stops short of naming the sibling it is not (e.g. clipember_create_client_connect_link or clipember_share_clip), so an agent must infer the distinction from the 'one post group' scope rather than being told.

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?

Usage context is clear: this is for client review/approval of a single post group's scheduled content, and an operational instruction is given ('give it to the user right away'). What is missing is explicit when-not-to-use guidance or a named alternative such as the client-connect link tool, so routing between the share tools is left partly to inference.

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