Skip to main content
Glama

List log label values

render_list_logs_values
Read-onlyIdempotent

Discover all distinct values for a given log label in Render logs. Filter by resource, time, text, and more to list matching label values.

Instructions

List log label values. List all values for a given log label in the logs matching the provided filters. Calls GET /logs/values 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.
labelYesThe label to query logs for
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 log label values 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.
Behavior3/5

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

Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that it operates on logs matching filters and invokes a specific API endpoint, which is useful but not rich behavioral context. It does not mention pagination behavior, rate limits, or that unique values are returned. No contradiction with 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 very short and front-loaded with the main purpose. However, the first sentence 'List log label values' is redundant with the title and does not earn its place. The remaining sentences are concise and informative, making it almost ideal but with a minor redundancy.

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?

With no output schema, the description does not explain return values, and it lacks details about behavior such as whether it returns distinct values or how pagination works. However, the input schema is comprehensive (covering all 18 parameters with defaults and examples) and annotations cover side-effect transparency. The description provides adequate context for a basic understanding but is not fully complete for a tool with this complexity.

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?

Input schema has 100% coverage, so the baseline is 3. The description mentions 'given log label' and 'provided filters' but adds no additional meaning beyond the schema's detailed per-parameter descriptions. It does not explain parameter interactions or output format, and with 18 parameters, the schema carries the full semantic burden.

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's purpose: 'List all values for a given log label in the logs matching the provided filters.' It specifies the action (list), the resource (log label values), and the scope (matching filters), and distinguishes it from sibling tools like render_list_logs or render_list_application_filter_values by focusing specifically on label values. The mention of the API endpoint adds precision.

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?

The description does not explicitly state when to use this tool over alternatives or mention exclusions. It implies usage for discovering possible values of a log label, but it lacks clear guidance such as 'use this to enumerate filter values' or 'for listing actual logs, use render_list_logs instead.' Thus, usage context is only implied, not explicitly communicated.

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