Skip to main content
Glama
Sign In
coolify-mcp

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_get_application_preview_logs

Retrieve runtime container logs for an application preview by pull request number (Coolify v4.3.23), with level/time/text filtering.

Instructions

Retrieve runtime container logs for an application preview by pull request number (Coolify v4.3.23), with level/time/text filtering.

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": {
      "uuid": "<uuid>",
      "pull_request_id": "<pull_request_id>"
    },
    "name": "coolify_get_application_preview_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNoReturn the most recent logs (tail behavior)
uuidYesUUID of the resource
levelNoMinimum log level to include
limitNoMaximum number of filtered log entries to return
linesNoServer log lines to fetch; all (or -1) fetches all. Defaults to limit. Filtering still caps the returned entries at limit.
sinceNoISO 8601 timestamp - only logs after this time
untilNoISO 8601 timestamp - only logs before this time
searchNoText to search for in log messages (case-insensitive)
service_nameNoCompose service whose container to read (Coolify v4.4+); defaults to the first container
pull_request_idYesPull request number of the preview
show_timestampsNoInclude server timestamps for accurate time filtering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.3.0
    • changedInput schema / properties / pull_request_id / description
      Previous value: -"ID of the resource"New value: +"Pull request number of the preview"
    • changedInput schema / properties / pull_request_id / maximum
      Previous value: -9007199254740991New value: +2147483647
    • addedInput schema / properties / service_name
      Added value: +{
+  "description": "Compose service whose container to read (Coolify v4.4+); defaults to the first container",
+  "minLength": 1,
+  "type": "string"
+}
  2. Addedv4.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states that it retrieves logs and supports filtering, but says nothing about authentication requirements, rate limits, ordering, behavior when the preview is missing, whether the operation is read-only, or other runtime characteristics.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It states the action, target, scoping key, and filtering support efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only log retrieval tool with 11 parameters and no output schema, the description is minimally adequate but incomplete. It does not describe the return structure or behavior around pagination, default service selection, or tail interactions, which are relevant when no output schema exists.

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 defines all 11 parameters, including level, time filters, tail, limit, and service_name. The description mentions level/time/text filtering but does not add syntax or semantics beyond what the schema provides, making the baseline 3 appropriate.

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 description uses a specific verb ('Retrieve') and resource ('runtime container logs for an application preview by pull request number'), clearly distinguishing this from generic log tools and other preview operations. It names the key scoping parameter and the filtering capabilities up front.

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?

It gives clear context for when this tool applies: retrieving logs for an application preview identified by PR number. However, it does not explicitly compare against sibling tools such as coolify_get_logs or coolify_get_application_preview, nor does it state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools