Skip to main content
Glama

Create an organization

create_organization

A new organization owned by you, with its own music, videos, Looks and credits Creates an empty organization (a workspace, in the app) with the signed-in person as its owner; with an API key, the member who created the key (the key needs organizations:write). type artist is for one artist (add that artist next with create_artist; its songs then need no artist_id), label for a roster. It starts with no plan and no credits, so nothing can be created in it until it has one. These credentials keep acting for their current organization: to work in the new one, sign in again and pick it, or create an API key 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": {
      "name": "<name>",
      "type": "<type>"
    },
    "name": "create_organization"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe workspace name, as people see it in the app (an artist workspace usually carries the artist name)
typeYesartist: one artist and its songs; label: a roster of artists (or a team working for them); creator: projects (artists in the API) whose performer is optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"artist: one artist and its songs; label: a roster of artists"New value: +"artist: one artist and its songs; label: a roster of artists (or a team working for them); creator: projects (artists in the API) whose performer is optional"
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "artist",
      -  "label"
      -]New value: +[
      +  "artist",
      +  "label",
      +  "creator"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"The organization name, as people see it in the app"New value: +"The workspace name, as people see it in the app (an artist workspace usually carries the artist name)"
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "artist: one artist and its songs; label: a roster of artists",
      +  "enum": [
      +    "artist",
      +    "label"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "name",
      +  "type"
      +]
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses the operational preconditions that matter most: the org starts with no plan and no credits so nothing can be created in it, the caller becomes owner (or the key's creator under an API key, requiring organizations:write), and existing credentials keep acting for their current org. Those are exactly the surprises an agent would otherwise hit after a successful call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is dense and useful, but the opening is a run-on fragment — "A new organization owned by you, with its own music, videos, Looks and credits" collides with "Creates an empty organization" with no punctuation, which obscures the front-loaded statement of purpose. The remaining sentences are tight but stacked as one long paragraph.

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 mutation tool with no output schema, the description covers auth, ownership, plan/credit state, and credential scoping thoroughly. It stops short of saying what the call returns (e.g. the new organization's identifier, needed for subsequent create_artist calls) and whether the name must be unique, which forces inference.

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 coverage is 100%, so baseline is 3, but the description adds downstream consequences of the `type` choice that the schema does not: an artist org takes a follow-up create_artist and its songs then need no artist_id, while label is for a roster. That meaningfully changes how an agent should pick the enum value.

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 ("Creates an empty organization") and immediately grounds it in domain terms ("a workspace, in the app") with the ownership rule. It also differentiates the three organization kinds and points to create_artist for the follow-up step, so an agent can distinguish it from siblings like list_organizations and update_organization.

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 clear guidance on which `type` to choose (artist vs label vs creator) and explicitly routes the agent to create_artist as the next step for artist organizations. It does not state when an agent should *not* create an organization (e.g. it already has one — see list_organizations), so the exclusion side is only implicit.

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