Imaginou

Create a public share link

create_share_link

Publishes one finished video of a completed production on a public, revocable Imaginou page (with a marketing banner). Defaults to the latest final video.

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": {
      "productionId": "<productionId>"
    },
    "name": "create_share_link"
  }
}

Input Schema

Name	Required	Description	Default
`mediaId`	No
`productionId`	Yes	Production ID (from list_productions or create_production).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely useful context the annotations do not: the page is public, carries a marketing banner, and is revocable. It stops short of saying that repeated calls create separate links (idempotentHint=false) or whether publishing can be undone other than via revoke.

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?

A single front-loaded sentence with the mutation, the target constraint, and the default all in the first clause. The parenthetical about the marketing banner is the only aside and it earns its place.

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

Completeness3/5

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

With no output schema, the agent gets no indication of what comes back — presumably a URL/id for the share link — nor what happens if the production is not finished. The creation semantics are solid, but the return contract is left implicit for a tool whose whole output is a link.

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 50% — mediaId has no schema description at all — but the sentence 'Publishes one finished video ... Defaults to the latest final video' supplies exactly the missing semantics: omitting mediaId selects the latest final video. It does not clarify whether mediaId may point to a non-final or non-video asset.

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?

Specific verb (publishes) plus a precise resource (one finished video of a completed production) and the artifact created (a public, revocable Imaginou page). The scope is narrowed enough that it cannot be confused with revoke_share_link or list_share_links.

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?

'of a completed production' states the precondition, and 'Defaults to the latest final video' tells the agent it may omit mediaId. It does not name the alternative paths (e.g., revoke_share_link for teardown, list_share_links for auditing), so a small inference remains.

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

All Imaginou tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?