GenFlick

social save motion preset

native.social_save_motion_preset

DestructiveIdempotent

Create, edit or archive one of the owner's motion presets: saved options on one canonical style, never code. Read the presets and their revisions from the workspace first (expectedRevision 0 creates). Posts that already used a preset keep the options they were given.

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

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

A3.9/5.0

Behavior4/5

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

Beyond the annotations, it discloses three behavioral facts: optimistic concurrency via revisions, that archives are one of the supported mutations, and that already-published posts using a preset keep the options they were given (i.e. edits are not retroactive). The annotations already declare destructiveHint=true and idempotentHint=true, and the description is consistent with both rather than contradicting them.

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?

Three short sentences, front-loaded with the operation and the object definition, then prerequisites, then the side-effect note. Dense but economical; the phrase 'never code' is slightly cryptic without expansion.

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?

For a mutating tool with a nested arguments object, revision control, and required skill proofs, the description covers the essential semantics: what a preset is, how to create vs edit, and the non-retroactive effect on existing posts. An output schema exists so return values need not be explained, but the invocation-plumbing parameters (request_key, read_skills, expected_catalog_version) rely entirely on the schema.

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 real meaning for expectedRevision (0 means create) and for the options/styleId pairing ('saved options on one canonical style'). However, it says nothing about work_id, request_key, archived, presetId, or the required read_skills proofs, which are the highest-risk parameters for a first-time caller.

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 set (create, edit, archive) against a specific resource (the owner's motion presets) and defines the object as 'saved options on one canonical style, never code,' which disambiguates it from code-level style tools. It does not name a sibling tool it might be confused with (e.g. social_save_draft), so it stops short of full differentiation.

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 an explicit prerequisite ordering: read the presets and their revisions from the workspace first, which tells the agent to use the read path before calling this. It also states the create-vs-edit trigger (expectedRevision 0 creates) but never states when not to use this tool or which sibling to prefer for adjacent social authoring.

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?