Skip to main content
Glama

Create Library folder

create_library_folder
Idempotent

Creates a folder under a visible Library parent, or under the root if parent_folder_id is omitted. Use the existing Library content tools with folder_id to group items in it.

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": {
      "idempotency_key": "<idempotency_key>",
      "name": "<name>"
    },
    "name": "create_library_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
idempotency_keyYes
parent_folder_idNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the root-default behavior, which is genuine behavioral context, but says nothing about what happens on duplicate names, what 'visible' constrains, or what a successful call yields.

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?

Two short sentences with zero filler, and the placement rule (the most decision-relevant fact) is front-loaded before the follow-up advice.

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 mutation tool with annotations and no output schema, the description covers creation placement but leaves gaps an agent would hit in practice: no return info (created folder id?), no name-conflict behavior, no explanation of the required idempotency_key, and no link to list_library_folders to discover a parent id.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains parent_folder_id's omission semantics well, but 'name' and the required idempotency_key are left entirely unexplained, and idempotency_key is the least self-evident parameter for an agent to supply correctly.

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 ('Creates a folder') and adds scope that separates it from siblings like get_library_folder or list_library_folders: it creates, they read. The 'visible Library parent, or under the root' clause further pins down where creation happens, though 'visible' is left undefined.

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?

The description gives a follow-up instruction (use the content tools with folder_id to group items) and the parent_folder_id omission rule, which is useful context. It never states when to choose this over alternatives such as create_collection, nor any prerequisites or exclusions, so usage is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources