Skip to main content
Glama

Manage project

manage_project

Create a project or change its state; nothing here deletes anything (permanent deletion is only in the web app, with a second factor). action create: a new project with development, preview and production environments, owned by the person behind this token; returns the id and slug the other tools take, fails on a slug in use, needs a token not limited to specific projects or environments, and a plan limit can refuse it. action update: rename the project or change its description (null clears it); the slug and contents stay, pass only what changes. action archive: make the project read-only for every member and token while reads keep working; use it when the user retires a project. action unarchive: make it writable again. Archive and unarchive are safe to repeat. Environments, deployment URLs and fields change through manage_project_details. Audited. Requires projects:write; every action but create also needs the owner role.

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": {
      "action": "<action>"
    },
    "name": "manage_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNocreate: required display name, 1 to 80 characters. update: the new display name
slugNocreate only: URL slug (lowercase letters, digits, dashes). Derived from the name when omitted
actionYesWhat to do
projectNoEvery action but create
descriptionNocreate, update: description, up to 500 characters; null clears it (update only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses failure modes (slug in use, plan limit), auth requirements (projects:write, owner role for all non-create actions), audit logging, and the precise semantics of archive (read-only for members and tokens while reads keep working). The statement that archive and unarchive are safe to repeat refines rather than contradicts the tool-level idempotentHint=false, which is dragged down by create.

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?

Front-loaded with the overall purpose, then organized as labelled per-action clauses; there is no filler and every clause carries a distinct constraint. The very dense semicolon-chained phrasing borders on a run-on, but nothing is redundant.

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 mutation tool with no output schema, it covers return values (the id and slug the other tools take), preconditions, failure cases, and post-state effects of archive. An agent has everything needed to choose an action and predict the outcome.

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 the baseline is 3, but the description adds real meaning: 'pass only what changes' establishes partial-update semantics, and it clarifies that null clears the description on update only and that project applies to every action but create. It does not restate the slug derivation rule in more depth than the schema already gives.

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-plus-resource ('Create a project or change its state') and then enumerates all four actions with their concrete effects. It also draws an explicit boundary against manage_project_details and against deletion, so an agent can place it among siblings 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 Guidelines5/5

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

Gives per-action selection guidance ('use it when the user retires a project'), an explicit when-not (nothing here deletes; permanent deletion is only in the web app) and a routing rule to manage_project_details for environments, deployment URLs and fields. Alternatives and exclusions are both named.

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