Skip to main content
Glama
0xtlt

coolify-mcp

by 0xtlt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

coolify_get_logs

Retrieve Coolify application logs with filters for log level, time range, or text search to isolate errors and analyze events.

Instructions

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

Input Schema

TableJSON 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)
show_timestampsNoInclude server timestamps for accurate time filtering

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv4.0.0

TDQS

B3.3/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 burden of behavioral disclosure. It states the action but does not disclose side effects, permission requirements, rate limits, pagination behavior, or the effect of combining filters like tail and limit. It does not mention that logs might be truncated or that timestamps are needed for accurate filtering. This is a minimal disclosure for a read operation.

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 sentence that front-loads the core purpose and lists the key filter dimensions concisely. There is no redundant or extraneous information, and it is appropriately sized for the tool's scope.

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 tool with 9 parameters, no output schema, and no annotations, the description is relatively sparse. It does not explain important behavioral details such as how tail interacts with limit, the difference between lines and limit, or the output format. While the schema covers parameter meanings, the description does not provide the necessary context for an agent to make informed decisions about when to use certain parameters or what to expect from the response. It is adequate but has clear gaps.

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 all 9 parameters have detailed descriptions in the schema. The tool description adds a high-level summary of filtering capabilities ('level, time range, or text search') that maps to the parameters, but it does not add meaning beyond what the schema already provides. Since the schema is comprehensive, a baseline of 3 is 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 clearly states the action ('Retrieve logs'), the target resource ('a Coolify application'), and the optional filters ('level, time range, or text search'). It is specific and distinguishes this tool from sibling log tools like coolify_get_database_logs and coolify_get_service_logs, which target other resource types.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives. It does not mention that this is specifically for application logs, nor does it state when to use the database or service log tools. There is no explicit when-to-use or when-not-to-use guidance, leaving the agent to infer from the tool name and sibling context.

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