Skip to main content
Glama

project_deploy_log

Read-onlyIdempotent

Get the build log for a deploy — the entry the bundler detected, every chunk it emitted with sizes, function bundle sizes, and any warnings. Compilation runs on the platform (you deploy raw source), so this is how you SEE what the build did — why CSS dropped, which chunk a warning came from — instead of reverse-engineering compiled output. Without version, it returns the latest deploy; a version from project_deploys returns a past one. Complements the build_log + rollback fields that project_deploy now returns inline.

Also surfaces failure context alongside (or instead of) a normal build log: last_failed_build (the most recent build that failed to compile), last_rejected (the most recent deploy rejected before compile, e.g. bundled-output detection), and recent_failures (up to 5 safe rows with failure_id, code, classification, message, remediation, known_cause, version, and at). somewhere api GET /v1/deploy/failure/<failure_id> resolves one exact reference. If the project has never had a successful deploy, version comes back null with an empty build_log and whatever failure context exists — that's the answer to "why did my first deploy fail," not an error.

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_deploy_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoDeploy version to fetch the log for (from project_deploys). Omitted: the latest deploy.
project_idYesProject ID, slug, subdomain, or 'default'.
release_idNoA release id from a deploy or patch response. Returns that release's blank-page check: post_live_render (status pending, clear, warned, rolled_back, ...), blank_page_check, and the DEPLOY_BLANK_PAGE `rejection` when the page rendered blank, including a release already rolled back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description goes well beyond that by explaining that compilation happens platform-side, that failure context (`last_failed_build`, `last_rejected`, `recent_failures`) is surfaced alongside the log, and that a project with no successful deploy returns `version: null` with an empty `build_log` rather than erroring. Those edge-case semantics are exactly the kind of behavior an agent cannot infer from structured fields.

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?

The core purpose and the version-selection rule are front-loaded in the first two sentences, before the failure-context detail. It is long and dense for a three-parameter tool, with some rhetorical phrasing ('instead of reverse-engineering compiled output') and a lengthy enumeration of `recent_failures` fields, but with no output schema much of that detail earns its place.

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?

With no output schema, explaining return values is the description's job, and it does so thoroughly: build log contents, failure-context fields, the redirect pointer for a single failure via the api path, and the null-version/empty-log case. An agent has enough to call it and interpret the result without further guidance.

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 the schema already documents all three parameters, making 3 the baseline. The description reinforces `version` semantics (latest vs. historical via `project_deploys`) but never mentions `release_id` or its blank-page-check behavior, so it adds only partial meaning beyond the schema.

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 ('Get the build log for a deploy') and immediately enumerates the content returned: the detected entry, every emitted chunk with sizes, function bundle sizes, and warnings. It also distinguishes itself from siblings by naming `project_deploys` as the source of version numbers and `project_deploy` as the tool returning build_log inline.

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 conditional routing: omit `version` for the latest deploy, pass a version from `project_deploys` for a past one, and use it to see why a build behaved a certain way rather than reverse-engineering output. It also preempts a misuse ('that's the answer to "why did my first deploy fail," not an error'). No explicit exclusion against adjacent tools like `project_logs` or `deploy_status`, which keeps it at 4.

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