Activity

Bug

When calling the deployment tool with action: "get" and lines: 10, the response includes the full raw JSON log output embedded in the logs field, resulting in a ~13.4k token response.

Expected behaviour

Requesting lines: 10 should return only the last 10 log lines, keeping the response compact. The lines parameter should truncate/limit the log output.

Actual behaviour

The full build log is returned in a single logs string field containing raw JSON entries. The response was ~13.4k tokens despite requesting only 10 lines.

Reproduction

mcp__coolify__deployment(action: "get", uuid: "<deployment-uuid>", lines: 10)

Impact

This fills up the LLM context window quickly when monitoring deployments, making it impractical to check build progress without burning through tokens.

Suggestion

• When lines is specified, only return the last N log entries
• Consider returning logs as a structured array rather than a raw JSON string
• The logs_info field (e.g. "Logs available (124654 chars). Use lines param to retrieve.") suggests the intent is to only include logs when lines is passed, but the truncation isn't working