Skip to main content
Glama

Create share link

create_share_link

Create a view-only link to the live preview for someone without a Mythex account. Not a publish — for showing work in progress. Links can be revoked.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoWho it is for, e.g. "client demo"
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds genuinely new context: the resulting link grants view-only access, is intended for unauthenticated outsiders (corroborating openWorld), and is revocable, which tells the agent the effect is recoverable. It omits whether links expire or whether repeated calls yield different URLs, but idempotentHint=false already signals the latter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and constrained by a clear negation. Every clause carries information an agent would otherwise have to guess.

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, non-destructive mutation this covers purpose, audience, access level, and reversibility. With no output schema, it would help to say that a share URL is returned, since the agent needs to know what the call yields, but that is the only material gap.

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 both parameters (name, project_id) are already documented including the "or use session from use_project" fallback. The description adds no meaning beyond the schema. Baseline 3 applies.

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?

"Create a view-only link to the live preview" gives a specific verb, resource, and scope (live preview, view-only), and "Not a publish" rules out a nearby concept an agent might confuse it with. It does not reference the actual siblings (list_share_links, delete_share_link), so the differentiation is against a capability rather than a tool.

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?

The audience condition is explicit: use this for someone without a Mythex account, to show work in progress, and explicitly not as a publish. That is a clear when-to-use and a when-not-to-use. It stops short of naming the sibling that revokes or lists links, so the agent must infer from "Links can be revoked" that a separate delete tool exists.

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