Skip to main content
Glama

project_deploys

Read-onlyIdempotent

List the recent deploy history for a project — successful deploys AND rejected/failed deploy attempts, interleaved by time (up to 150 successful releases plus 20 failed attempts). Each entry has a status field so you can tell a success from a rejection at a glance.

Example:

{ "project_id": "my-saas" }
// Returns: { "deploys": [
  { "status": "success", "version": 12, "promoted_at": "2026-04-20T...", "is_live": true, "commit_sha": "...", "deployed_by": { "user_id": "...", "email": "..." } },
  { "status": "rejected", "version": 11, "reason": "BUNDLED_DEPLOY_REJECTED", "message": "This looks like pre-built output...", "at": "2026-04-19T...", "is_live": false },
  { "status": "success", "version": 10, "promoted_at": "2026-04-18T...", "is_live": false }
] }

A rejected entry's version is the version it WOULD have become (may be null); it never went live. Each successful entry carries rollback_available, describing retained build availability. A false entry cannot be restored; true still requires schema-safe activation. project_rollback selects the previous activation; project_restore_version selects a retained version by number. Free covers the last 24 hours. Paid plans cover any retained version. Failure entries also include failure_id, a safe classification, and remediation. somewhere api GET /v1/deploy/failure/<failure_id> resolves one exact reference; the endpoint requires access to the owning project and never returns the private stack or provider diagnostic.

Each successful version shows its user-supplied note, if any, and the restore call when available. You can add a note when publishing or later. Each successful entry also carries build: { recorded: true, reported_cli_version, platform_version_id, platform_version_tag, runtime_build_version } — the CLI version the deploying client reported (its own claim, null when none was sent, e.g. an MCP deploy), the API build that published the release (the separate compiler build is not recorded), and the runtime build baked into its functions (null without functions). A release built without identity recording (including by older code during rollback) returns { recorded: false, reason: 'built_without_identity_recording' }; it is never guessed.

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": {
      "project_id": "<project_id>"
    },
    "name": "project_deploys"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID, subdomain, or 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered, and the description still adds real behavioral context: result caps (150 successes plus 20 failures), plan-dependent retention (free = last 24 hours, paid = any retained version), that rejected versions never went live, and that the failure-resolution endpoint requires access to the owning project and never exposes private stacks or provider diagnostics. The one gap is that it does not state pagination or ordering behavior for very large histories.

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 purpose and limits are front-loaded and the worked example is genuinely clarifying. However, the text then drifts into deep return-value internals — build identity recording, why a release may return recorded:false, rollback schema-safety caveats — that are verbose relative to the decision the agent is making. With no output schema some of this earns its place, but it could be trimmed considerably.

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?

With no output schema, the description must carry return-value documentation, and it does so thoroughly: entry shapes for success and rejection, the rollback_available flag, failure_id/classification/remediation, and how to resolve a failure reference. A one-parameter, read-only tool is well served by this; the only shortfall is the absence of any note on result ordering beyond 'interleaved by time' and no mention of pagination.

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?

There is a single required parameter and the schema describes it at 100% coverage ('Project ID, subdomain, or default'), so the structured field already carries the meaning. The example supplies a concrete value ('my-saas'), but nothing about the parameter's semantics is added 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?

The first sentence names a specific verb and resource ('List the recent deploy history for a project') and makes the scope explicit: successes and rejected/failed attempts interleaved by time. The status-field sentence tells the agent the output is self-classifying, so it is clearly distinguishable from a single-deploy or log tool.

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

Usage Guidelines3/5

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

Usage is only implied — the agent can infer this is the read step before acting. The description does route the reader toward follow-ups ('project_rollback selects the previous activation; project_restore_version selects a retained version by number'), which is useful adjacency guidance. But there is no explicit statement of when to prefer this over siblings such as project_deploy_log or project_deploy, and no exclusion guidance.

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