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 creating prompts. Optionally nest it 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

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

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. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 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"
+}
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower. The description adds real value beyond them by stating 'does not move any prompts' — ruling out a side effect an agent might otherwise fear — and noting the returned id and slug.

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?

Three sentences, front-loaded with the core action, with each subsequent sentence carrying a distinct fact (prerequisite context, nesting, return/side-effects). Minor redundancy with the schema on parent_collection_id keeps it from a 5.

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?

For a three-parameter creation tool with full schema coverage and an output schema, the description covers purpose, prerequisite timing, nesting behavior, and side-effect scope. Nothing an agent needs to call it correctly is missing.

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 100%, so all three parameters are already documented. The description's note about parent_collection_id nesting essentially restates the schema's own wording, adding no new syntax or format detail. Baseline 3 applies.

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 and resource ('Create a new prompt collection') plus its scope ('organizing prompts by app'), which cleanly separates it from update_collection, list_collections, and delete_collection. An agent can identify the operation without opening the schema.

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 an explicit trigger ('when you need a new namespace before create_prompt') and routes to the nesting case via parent_collection_id. It does not mention when to prefer update_collection for an existing collection, but the pre-creation context is clear.

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