GenFlick

Start, pause or archive an automation

native.set_automation_state

DestructiveIdempotent

Start (active), pause or archive an automation. Pausing stops future runs; a run already working finishes and has its own Stop. Starting an automation that needs the owner's approval is refused until they approve it in Genflick.

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.set_automation_state"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact 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_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare the tool mutating and destructive, so the bar is lower, yet the description still adds real behavioral context: the partial-effect semantics of pause and the approval gate that can cause a start to fail. It does not say what archiving actually does to the automation (reversible? data retained?) or that a stale expected_revision will be refused.

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 with no filler; the valid states come first and the two failure-relevant caveats follow. Every sentence carries actionable information.

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?

An output schema exists, so return values need no explanation, and the description covers the state semantics and the approval refusal that matter most for correct invocation. The session-bootstrap parameters (read_skills, expected_catalog_version, request_key) are left entirely to the schema, which is the main remaining gap for a six-parameter tool.

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 50%, and the description adds meaning for the state value (mapping "start" to active and clarifying pause vs. archive), which is genuinely useful beyond the bare enum. However, it says nothing about work_id, request_key, read_skills, expected_catalog_version, or publication_proposal_id, leaving half the parameters documented only in the schema or not at all.

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 names a specific verb ("Start, pause or archive") and resource ("an automation") and enumerates the three target states, so the agent knows exactly which mutation this performs. It implicitly separates itself from siblings that run (run_automation_now) or stop a run (stop_automation_run) by noting a running instance "has its own Stop", but it never names those siblings outright.

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 gives clear contextual guidance: pause suppresses future runs only, in-flight runs complete, and starting an unapproved automation is refused until owner approval. What is missing is any explicit routing to alternatives such as native.save_automation (changing the definition) or native.run_automation_now (executing once).

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

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