Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

create element folder

native.create_element_folder
DestructiveIdempotent

Create a folder tile in one Elements tab, optionally nested under an exact parent ID or path. Reuses an existing sibling with the same name.

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

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.2/5.0
Behavior3/5

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

The sentence 'Reuses an existing sibling with the same name' genuinely adds value beyond the annotations, explaining the idempotentHint=true behavior in concrete terms. However, with destructiveHint=true declared, the description says nothing about what collision/reuse means for the existing tile, nor about the read_skills or expected_catalog_version gating that govern whether a call will be accepted.

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 followed by the nesting constraint and the dedup behavior. No filler; only a slight loss for packing two distinct ideas (nesting and reuse) into one compressed line.

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

Completeness3/5

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

For a 6-parameter, 5-required mutation tool with nested objects, the description covers the core action, nesting, and name-collision behavior, and an output schema exists so return values need not be explained. It falls short on the session/proof parameters (read_skills, expected_catalog_version) that determine whether the call succeeds.

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?

The description clarifies that parent_folder_id and parent_folder_path are alternatives ('an exact parent ID or path'), which the schema leaves implicit, and 'one Elements tab' maps to the lane enum. But work_id and request_key carry no schema descriptions and no explanation here, and the read_skills proof requirement is only documented in the schema, so coverage of 50% is not fully 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?

States a specific verb and resource: 'Create a folder tile in one Elements tab', plus the nesting capability. It implicitly separates itself from generic folder/element creators by scoping to the Elements tab, but never names siblings like create_folder or create_document_folder, so an agent must infer the distinction.

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 explicit when-to-use guidance and no mention of when NOT to use it or which sibling to pick instead (e.g., create_folder vs create_document_folder). The only usage signal is the implied 'Elements tab' scope carried in the purpose sentence.

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