Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_get_logs

Retrieve logs for a Coolify application with optional filtering by level, time range, or text search

Instructions

Retrieve logs for a Coolify application with optional filtering by level, time range, or text search

Input Schema

NameRequiredDescriptionDefault
tailNoReturn the most recent logs (tail behavior)
uuidYesUUID of the application
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
show_timestampsNoInclude server timestamps for accurate time filtering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.3.0
    • 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. Changed4 schema fields changedv4.1.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of log entries to fetch from the server"New value: +"Maximum number of filtered log entries to return"
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / lines
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 10000,
+      "minimum": -1,
+      "type": "integer"
+    },
+    {
+      "const": "all",
+      "type": "string"
+    }
+  ],
+  "description": "Server log lines to fetch; all (or -1) fetches all. Defaults to limit. Filtering still caps the returned entries at limit."
+}
    • addedInput schema / properties / show_timestamps
      Added value: +{
+  "default": true,
+  "description": "Include server timestamps for accurate time filtering",
+  "type": "boolean"
+}
  3. First observedv4.0.0

TDQS

B3.2/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, and it discloses almost nothing beyond "retrieves". It doesn't say the read is non-destructive, that results are capped (limit default 100, max 1000), that lines/tail control how much raw log is pulled, that filtering truncates output, or that service_name defaults to the first container. All of that lives only in schema parameter descriptions, leaving the agent's mental model of the operation thin.

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?

A single front-loaded sentence with the verb, resource, and the three filter categories — nothing wasted. It is arguably too terse for a 10-parameter tool, but the sentence itself is well-formed and uncluttered.

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 fetch with 10 parameters, 100% schema coverage and no output schema, the description does the minimum: it tells the agent what it gets and what it can filter on. It omits the interaction between lines/tail/limit, the default-to-first-container behavior of service_name, and any sense of the return shape (array? raw text? entries with timestamps?). Adequate, not complete.

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 explains every parameter including level, since/until, search, tail, and limit. The description only echoes the three filter categories (level, time range, text search) and adds no syntax, precedence, or defaulting semantics beyond that. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Retrieve logs for a Coolify application") and names the filtering axes, and the phrase "for a Coolify application" implicitly separates it from coolify_get_database_logs / coolify_get_service_logs / coolify_get_application_preview_logs. It stops short of explicitly naming those siblings, so the differentiation is inferred rather than stated.

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 tell this is the tool for application logs with optional filtering, but there is no "use this when X, use coolify_get_service_logs when Y" guidance and no prerequisites (application must exist / be deployed). The optional filters are mentioned but not when to combine them.

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