Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Save a brief in a linked GenAds project using its native command and exact observed revision

native.save_genads_brief
DestructiveIdempotent

Save a brief in a linked GenAds project using its native command and exact observed revision. Zero creates a resource.

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_genads_brief"
  }
}

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

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds real behavioral context by requiring "the exact observed revision", which implies optimistic-concurrency checking against a previously read state, but it never says what gets overwritten or why the operation is flagged destructive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no padding, so it is concise by length. However, the second sentence is an opaque fragment that consumes space without conveying actionable meaning, and the definition is under-specified rather than trimmed to essentials.

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?

This is a complex mutation with a nested body, five required parameters, open-world and destructive semantics, and many near-identical GenAds siblings. The description does not cover when to prefer it, what the request_key/idempotency contract is, or what a stale revision produces, so an agent could easily invoke the wrong save/update tool or supply a mismatched revision.

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 description explains only expected_revision ("exact observed revision"); work_id, arguments, request_key, and the nested body fields are left to the schema. The phrase "exact observed revision" does add meaning beyond the bare integer type, but the remaining high-consequence parameters, especially request_key and the idempotency contract, receive no treatment.

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 a brief in a linked GenAds project" gives a specific verb and resource, and adds the mechanism (native command) and constraint (exact observed revision). It does not explicitly distinguish itself from close siblings such as native.genads_save_brief or native.update_brief, and the trailing sentence "Zero creates a resource" is cryptic rather than clarifying.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus native.genads_save_brief, native.update_brief, or the studio-level save path, all of which appear in the sibling list. The only conditional-sounding sentence, "Zero creates a resource", is too ambiguous to act on and could refer to revision 0, request_key, or a count of resources created.

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