Skip to main content
Glama

Create Workspace

create_workspace

Create a workspace in the organization of the workspace the call acts in (the current one unless workspaceId names another). Every organization owner and admin becomes its admin. Returns the workspace with id, name, description, organizationId, isDefault, connectionLimit and createdAt; pass id as workspaceId to act in it, for example to send_invitation or create_connect_link there. Needs the workspace.manage permission, which Admin holds. The member who created the key, or the signed-in member, must also be an organization owner or admin (org-owner or org-admin); otherwise it fails with 403 permission_denied. Fails with 403 subscription_required when the plan has no room for another workspace (the error names the limit and current usage): tell the user to upgrade and do not retry. Fails with 400 when a workspace with this name already exists in the organization.

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>"
    },
    "name": "create_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWorkspace name, unique within the organization. No < or >
descriptionNoOptional description, up to 500 characters. No < or >
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another
connectionLimitNoMost social accounts the workspace may connect. Leave out for no limit

Output Schema

NameRequiredDescriptionDefault
resultYesThe workspace: id, name, description (null when none), organizationId, isDefault, connectionLimit (null for no limit) and createdAt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false) by disclosing the side effect that every org owner and admin becomes an admin of the new workspace, the full failure surface with codes and causes (403 permission_denied, 403 subscription_required with the instruction not to retry and to tell the user to upgrade, 400 name collision), and the returned fields. Nothing in the description contradicts the annotations.

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?

Purpose and scope are front-loaded in the first sentence, then permissions and error behavior follow in a logical order. It is dense with semicolon-chained clauses, but each sentence carries distinct operational information rather than restating the name or schema.

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 create tool with a mutation annotation set, four documented parameters and an output schema, the description covers everything an agent needs: where the workspace lands, who gets admin, the permission and role requirements, the returned id and how to reuse it, and how each error should be handled. No gap remains that would cause a misinvocation.

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 the schema already documents `name`, `description`, `workspaceId`, and `connectionLimit` thoroughly. The description reinforces `workspaceId` semantics ('the current one unless workspaceId names another') and adds the uniqueness/400-conflict meaning of `name`, but adds nothing about `connectionLimit` or `description` beyond the schema. 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?

Opens with a specific verb+resource ('Create a workspace') and immediately scopes it: the workspace is created in the organization of the workspace the call acts in, with `workspaceId` able to name another. That level of scoping detail lets an agent distinguish this from sibling creation tools such as create_connect_link or send_invitation without opening a 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?

The description gives real preconditions and follow-on guidance: it needs the workspace.manage permission, the caller must be an org owner or admin, and the returned `id` should be passed as `workspaceId` to later tools like send_invitation or create_connect_link. It does not name any when-not-to-use condition, but no plausible alternative tool exists for this action.

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