Skip to main content
Glama

List logs

render_list_logs
Read-onlyIdempotent

Fetch filtered logs from Render resources by time, resource, type, and other criteria. Use start and end timestamps to paginate through complete log history.

Instructions

List logs. List logs matching the provided filters. Logs are paginated by start and end timestamps. There are more logs to fetch if hasMore is true in the response. Provide the nextStartTime and nextEndTime timestamps as the startTime and endTime query parameters to fetch the next page of logs. 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 on the Render Public API. Usage: Requires an ownerId and a resource array of ids. For the common case — recent logs for one service — render_recent_logs takes a service name and fills both in.

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.
Behavior5/5

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

Annotations already indicate readOnly and non-destructive behavior, but the description adds important behavioral details: pagination via start/end timestamps, the hasMore flag, and the need to pass nextStartTime/nextEndTime for subsequent pages. It also discloses the cross-region/owner restriction and the underlying GET /logs API call, which goes beyond the annotations.

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?

The description is well-structured and front-loaded, but opens with a slight redundancy ('List logs. List logs matching the provided filters.'). The rest of the sentences each add meaningful detail without bulk, making the description appropriately sized for the tool's complexity.

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

Completeness4/5

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

With 17 parameters, a non-trivial pagination model, and a sibling alternative, the description covers the essential usage, cross-resource constraints, and pagination mechanics. It lacks a full return-value specification, but there is no output schema and the description already mentions hasMore and the pagination fields, so the completeness is strong but not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents all 17 parameters with descriptions (100% coverage), so the baseline is 3. The description adds extra meaning by identifying ownerId and resource as required, explaining the pagination parameters (nextStartTime/nextEndTime mapping to startTime/endTime), and noting the filters as a group. This adds value beyond the schema.

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 states a specific verb and resource: 'List logs matching the provided filters.' It distinguishes from sibling tools by referencing render_recent_logs for the common case and by detailing the paginated listing behavior. It clearly identifies the tool's scope as a general log listing operation.

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

Usage Guidelines5/5

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

The description explicitly names render_recent_logs as the preferred alternative for recent logs of a single service, and states the required inputs (ownerId and resource array). It also specifies the constraint that all queried resources must be in the same region and belong to the same owner, giving clear when-to-use 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