Skip to main content
Glama
Sign In

ScreenWeaver

by ai.screenweaver
OverviewDiscussionsAdmin

Create project

create_project

Create a new ScreenWeaver project with an empty script, in an organisation where you are an owner or editor. Ask the user for the title and whether it is a film (scriptMode STANDARD) or a series (EPISODICAL) when they have not said. orgId comes from list_organisations; when there are several, ask the user which one. It can be left out only when you belong to exactly one. aspectRatio (16:9, 9:16, 2.39:1, 4:3, 3:4) is optional; set it only when the user chose one. Pass a requestId you generate (8 to 64 letters, digits, - or _) and reuse it if you retry: a repeat returns the same project (reused: true) instead of creating a second one. Returns projectId, path and url (the project's link; give it to the user). Use projectId with the other tools to write to the new project. Projects cannot be deleted through these tools.

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganisation id from list_organisations.
titleYesProject title.
localeNoLanguage of the empty script's placeholders (default en).
requestIdNoIdempotency key: reuse it when retrying the same create.
scriptModeYesSTANDARD for a film, EPISODICAL for a series.
aspectRatioNoFrame shape the user chose: 16:9, 9:16, 2.39:1, 4:3, 3:4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / locale / enum
      Previous value: -[
-  "en",
-  "fr"
-]New value: +[
+  "en",
+  "fr",
+  "ko"
+]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the required permission level, that the project starts with an empty script, the idempotency contract via a caller-generated requestId (repeat returns the same project with reused: true), and the important permanence fact that projects cannot be deleted through these tools. The requestId dedupe is keyed idempotency rather than natural idempotency, so it does not contradict idempotentHint=false.

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?

Front-loaded with the action, then prerequisites, then retry semantics, then return values — a sensible order with no filler. It loses a point for mild duplication: the aspectRatio enum values and the scriptMode mapping are restated from the schema, which the agent already has.

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?

With no output schema, the description correctly takes on the return-value burden: projectId, path and url, plus the instruction to surface the link and to use projectId with downstream tools. For a 6-parameter creation tool with an org prerequisite, nothing material is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description still adds meaning the schema cannot: orgId's provenance and the condition under which it can be omitted, scriptMode mapped to the user-facing film/series decision, aspectRatio framed as opt-in only on user choice, and requestId's format-plus-retry lifecycle.

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?

States a specific verb and resource ("Create a new ScreenWeaver project with an empty script") and immediately narrows scope with the permission constraint (owner or editor). This clearly distinguishes it from list_projects, get_project_outline and the many shot/script tools in the sibling set.

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

Usage Guidelines5/5

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

Gives explicit decision rules: ask the user for title and scriptMode when unstated, get orgId from list_organisations, ask which org when several exist, omit only when the caller belongs to exactly one, and set aspectRatio only when the user chose one. These are when-to-use and when-not-to-use instructions plus the named alternative source for orgId.

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

All ScreenWeaver 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