Skip to main content
Glama
Sign In

CutClip.one

by one.cutclip
OverviewDiscussionsAdmin

storyline.get

Fetch the Scenario Maker draft storyline for a project: the premise (and how many reference images it has), the scenes the user has accepted so far (path), and the current batch of suggested next scenes (candidates).

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": {
      "projectId": "<projectId>"
    },
    "name": "storyline.get"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Fetch' implies a read with no side effects, and the description usefully discloses the shape of what comes back (premise plus reference-image count, accepted scene path, candidate batch). It does not state whether the operation is side-effect free, whether it errors when no draft exists, or any permission constraints.

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?

One dense sentence, front-loaded with the verb and resource, then the three payload components in a readable parenthesized list. No filler, though the nested parentheticals make it slightly harder to scan than a short bulleted breakdown.

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?

There is no output schema, so the description must describe the return value, and it does so thoroughly by naming the premise, path, and candidates fields. For a single-parameter read tool this is close to complete; the main residual gap is the absence of error or empty-state behavior.

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 0% and the single parameter projectId is undocumented in the schema. The description only implies scoping via 'for a project', without stating the ID format, source, or behavior for an invalid or draft-less project. Modest value added over the bare schema.

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 specific verb and resource ('Fetch the Scenario Maker draft storyline for a project') and then enumerates the payload (premise, accepted scenes, candidate scenes). It is clearly distinguishable from the mutating siblings (storyline.pick, storyline.apply, storyline.suggest) by virtue of being a read. It stops short of explicitly naming those siblings as alternatives, so it is a 4 rather than a 5.

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 only implied: 'fetch the draft storyline' suggests the state-read step of the Scenario Maker workflow, and the mention of 'accepted so far' and 'suggested next scenes' hints at the review loop with storyline.pick. There is no explicit when-to-use or when-not-to-use statement and no reference to a sibling tool.

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

All CutClip.one toolsInspect
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