Skip to main content
Glama
CodesWhat

portkey-admin-mcp

by CodesWhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_collection

Create a new prompt collection to organize prompts by app and establish a namespace before adding prompts. Optionally nest under a parent collection; returns the collection ID and slug.

Instructions

Create a new prompt collection for organizing prompts by app. Use this when you need a new namespace before create_prompt; set parent_collection_id to nest it under an existing collection. Returns the collection id and slug, and does not move any prompts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCollection name (e.g., 'hourlink', 'apizone', 'research-pilot')
workspace_idNoWorkspace ID to create collection in
parent_collection_idNoID or slug of the parent collection to nest under; omit for a top-level collection

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / parent_collection_id
      Added value: +{
+  "description": "ID or slug of the parent collection to nest under; omit for a top-level collection",
+  "type": "string"
+}
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With annotations covering the safety profile (readOnly=false, destructive=false, openWorld=true), the description adds genuinely useful behavior: it returns the collection id and slug and explicitly states it 'does not move any prompts' — a real side-effect clarification. It stops short of covering idempotency or permission requirements.

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?

Three tight sentences, purpose front-loaded, then usage, then the parent_id tip and return/side-effect note. Every sentence carries information an agent needs.

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

Completeness5/5

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

An output schema exists, so return values do not need explaining, yet the description still flags the id/slug return and the absence of prompt movement. Combined with full schema coverage and annotations, nothing material is missing for a create operation.

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 description coverage is 100%, so all three parameters are already documented. The description's note on parent_collection_id and workspace nesting largely restates the schema, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Create a new prompt collection') plus its domain purpose ('organizing prompts by app'), which separates it cleanly from siblings like create_prompt, update_collection, and list_collections.

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

Usage Guidelines4/5

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

Gives concrete when-to-use guidance ('Use this when you need a new namespace before create_prompt') and a nesting condition. It does not name an explicit alternative tool or a when-not-to-use case, so it falls just short of a 5.

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