Skip to main content
Glama

Share flow

share_flow
Idempotent

Create or refresh a public read-only link anyone can open for a Wavelength flow, with no account needed. Optionally include a summary shown on the public page. hide_attribution is Pro only and the server enforces it. Returns the public url, slug, and is_public flag. Also returns embed_image_url, a live SVG image of the flow that updates when the flow changes, and embed_markdown, ready to paste into Notion, Confluence, GitHub, or any Markdown page. Pass password to protect the link with a password.

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": {
      "flow_id": "<flow_id>"
    },
    "name": "share_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_idYesThe id of the flow to share.
summaryNoOptional summary shown on the public page, up to 300 characters.
passwordNoOptional. 6 to 128 characters. Only people with the password can open the link. An empty string removes the password. A protected link has no embed or image link.
hide_attributionNoOptional. Hide the Wavelength attribution on the public page. Pro only; the server enforces the plan limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / password
      Added value: +{
      +  "description": "Optional. 6 to 128 characters. Only people with the password can open the link. An empty string removes the password. A protected link has no embed or image link.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds real behavioral context: Pro-only attribution hiding enforced server-side, the returned url/slug/is_public, live-updating embed assets, and the side effect that a password-protected link loses its embed. That is meaningful beyond the structured fields, though error or missing-flow behavior is not covered.

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?

The purpose is front-loaded in the first sentence and the return-value details follow logically. A couple of sentences duplicate what the schema already states about password and Pro enforcement, which is modest waste but not disruptive.

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?

With no output schema, the description usefully enumerates the return payload (url, slug, is_public, embed_image_url, embed_markdown). For a mutating, open-world sharing tool it leaves only minor gaps, such as behavior when flow_id is invalid or the caller lacks permission.

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 every parameter is already documented, including password character limits and the empty-string reset. The description largely restates those rules for password and hide_attribution rather than adding new semantics, so the baseline 3 is appropriate.

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 opens with a precise verb and resource: 'Create or refresh a public read-only link anyone can open for a Wavelength flow.' That clearly establishes an upsert-style sharing operation. It does not name nearby siblings such as unshare_flow or get_share_status, so the agent must infer where this sits relative to them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'create or refresh' — the tool doubles as an update path for an existing link — and the password sentence signals an optional hardening mode. There is no explicit when-to-use versus when-not, and no pointer to unshare_flow for revocation or get_share_status for inspection.

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