Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

save social example

native.save_social_example
DestructiveIdempotent

Save or unsave an observed example for this studio. Free; does not download video or generate content.

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

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

B3.1/5.0
Behavior3/5

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

With annotations already declaring destructiveHint=true, idempotentHint=true, and openWorldHint=true, the description usefully adds that the call is free and does not download video or generate content, which curbs cost anxiety. However it never states what an unsave removes (the example from the studio's saved set), whether the operation is reversible, or why the destructive hint is set — the very thing an agent would want explained given the conflicting "Free; does not..." framing.

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?

Two short sentences, front-loaded with the action, and the second sentence earns its place by pre-empting a cost/generation concern. It is efficient and wastes no words, though the "Free; does not..." clause prioritizes reassurance over the missing call mechanics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has six parameters, five required, a nested arguments object, and a heavy invocation envelope (work_id, expected_catalog_version, read_skills, request_key), yet the description says nothing about that envelope. An output schema exists so return values need not be explained, but for a mutation with 50% schema coverage the description leaves far too much for the agent to infer.

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

Parameters2/5

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

Only three of six parameters (read_skills, publication_proposal_id, expected_catalog_version) carry schema descriptions, and the description adds no meaning to any of them. Critically, the nested arguments object with its saved boolean, example_id, and media_item_id — the actual payload that determines whether the call saves or unsaves — is not mentioned at all, so the missing schema coverage is not compensated.

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?

"Save or unsave an observed example for this studio" names a specific verb pair (save/unsave), the resource (an observed example), and the scope (this studio), so it is clearly distinct from the sibling native.read_social_example. It stops short of 5 because "observed example" is a domain term left unexplained and the toggle nature of a single call is only implied by "or".

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: calling this on an "observed" example suggests the example must first be read via native.read_social_example. There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing tells the agent how this differs from other social save tools such as native.social_save_draft or native.social_save_policy.

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