Skip to main content
Glama
Sign In
Unilytics MCP Server

Unilytics MCP Server

Official
by TeamUnilytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_folder

Creates a folder within a project to group related skills, knowledge-base files, and memory into one working context.

Instructions

Create a folder (Context) inside a project to organize skills + files.

A folder groups a related set of skills (e.g. a "Content Refresh" folder),
its knowledge-base files, and its memory: the project's working context.

Args:
    project_id: The project UUID (from list_projects or create_project).
    name: The folder name (e.g. "Content Refresh").

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": {
      "project_id": "<project_id>",
      "name": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
-  "default": null,
-  "title": "config",
-  "type": "string"
-}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful context about what a folder contains (skills, files, memory), but says nothing about duplicate-name behavior, permissions, or what is returned on creation.

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?

The purpose is front-loaded in the first sentence, followed by a short explanatory paragraph and a compact Args block. Every line is relevant, with only minor redundancy between the opening sentence and the folder explanation.

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 simple two-parameter creation tool with no output schema, the description covers purpose, the conceptual role of the created object, and both parameters. Missing only edge-case behavior, which is a modest gap given the tool's simplicity.

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

Parameters4/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 the parameter burden, and it does: project_id is identified as a project UUID sourced from list_projects or create_project, and name is given a concrete example. It stops short of format constraints such as length or allowed characters.

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 (Context) inside a project') and explains what a folder is: a grouping of related skills, knowledge-base files, and memory. It scopes the operation to a project, which separates it from create_project, though it never names a sibling explicitly.

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 implied by the explanation that a folder organizes skills and files, so an agent can infer it should be called before adding skills to a folder. There is no explicit when-to-use/when-not guidance and no mention of alternatives such as create_project.

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

Deploy Server

Other Tools