Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

link film studio document

native.link_film_studio_document
DestructiveIdempotent

Add a Series document to a linked Film project as the same living file. Edits in either studio update both. Repeated calls adopt the existing link. Use the Series document ID from read_resource; context_refs alone do not add a file to Film Documents.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.link_film_studio_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
argumentsYes
read_skillsYesExact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
request_keyYes
publication_proposal_idNoFor native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
expected_catalog_versionYesFor a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare idempotentHint=true and destructiveHint=true; the description usefully explains the underlying mechanics behind both — repeated calls adopt the existing link, and edits propagate to both studios because the file is shared. It stops short of spelling out what is mutated or what permissions are needed for an openWorld mutation, so it adds context without fully covering the destructive scope.

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?

Four short sentences, front-loaded with the action and the shared-file consequence before the preconditions. Every sentence carries information, though 'context_refs alone do not add a file to Film Documents' leans on internal jargon that costs a little clarity.

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 an output schema present, return values need no explanation, and the description covers the core semantics of the link and its idempotency. For a 6-parameter nested mutation it leaves folder placement and the work_id/request_key plumbing to the schema, which is acceptable but not exhaustive.

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 coverage is 50% and the nested arguments object (project_id, document_id, folder_id) is undocumented in the schema. The description recovers document_id ('Series document ID from read_resource') and implicitly identifies project_id as the Film project, but work_id, request_key, and folder_id get no explanation, so compensation is partial.

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 gives a concrete verb and resource ('Add a Series document to a linked Film project') plus a clarifying model of the result ('same living file'). It separates itself from read_resource and from context_refs, but never distinguishes itself from the sibling link_series_film, which an agent could easily confuse with this 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?

It states a real precondition ('Use the Series document ID from read_resource') and rules out a tempting wrong path ('context_refs alone do not add a file to Film Documents'). What is missing is an explicit when-not or a named alternative such as link_series_film / unlink_series_film.

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

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