Skip to main content
Glama

Subscribe to new logs

render_subscribe_logs
Read-onlyIdempotent

Subscribe to real-time logs from Render. Open a websocket and stream log entries matching filters like resource, text, and time, across resources in the same region and owner.

Instructions

Subscribe to new logs. Open a websocket connection to subscribe to logs matching the provided filters. Logs are streamed in real-time as they are generated. You can query for logs across multiple resources, but all resources must be in the same region and belong to the same owner. Calls GET /logs/subscribe on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoFilter request logs by their host. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
pathNoFilter request logs by their path. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
taskNoFilter logs by their task(s)
textNoFilter by the text of the logs. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
typeNoFilter logs by their type. Types include `app` for application logs, `request` for request logs, and `build` for build logs. You can find the full set of types available for a query by using the `GET /logs/values` endpoint.
levelNoFilter logs by their severity level. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
limitNoThe maximum number of items to return. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
methodNoFilter request logs by their requests method. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
endTimeNoEpoch/Unix timestamp of end of time range to return. Defaults to `now()`.
ownerIdYesThe ID of the workspace to return logs for
sandboxNoFilter logs by sandbox ID.
taskRunNoFilter logs by their task run id(s)
instanceNoFilter logs by the instance they were emitted from. An instance is the id of a specific running server.
resourceYesFilter logs by their resource. A resource is the id of a server, cronjob, job, postgres, redis, workflow, or sandbox group.
directionNoThe direction to query logs for. Backward will return most recent logs first. Forward will start with the oldest logs in the time range.backward
startTimeNoEpoch/Unix timestamp of start of time range to return. Defaults to `now() - 1 hour`.
statusCodeNoFilter request logs by their status code. [Wildcards and regex](https://render.com/docs/logging#wildcards-and-regular-expressions) are supported.
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: websocket connection, real-time streaming, resource constraints, and the API endpoint. It goes beyond annotations but doesn't cover the full connection lifecycle.

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 three sentences and front-loaded with the core action. Each sentence adds distinct value: websocket connection, real-time streaming, and constraint/endpoint info. No filler.

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?

The description explains the streaming behavior and constraints, but with no output schema and a complex websocket subscription, it doesn't cover return format or connection lifecycle (e.g., how to close, how limit applies). Some gaps remain for a fully self-sufficient description.

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 baseline is 3. The description adds some context about multi-resource queries and regional/owner constraints, but doesn't elaborate on individual parameters beyond what the schema already provides.

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 tool subscribes to new logs via a websocket, with real-time streaming. It distinguishes from siblings like render_list_logs or render_recent_logs by emphasizing the streaming nature of the subscription.

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?

The description clearly implies real-time streaming as the use case, and notes constraints (same region, same owner). It does not explicitly name alternatives or when-not-to-use, but the real-time context provides clear guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LuSrodri/render-useful-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server