Skip to main content
Glama

List log label values

render_list_logs_values
Read-onlyIdempotent

Retrieve all distinct values for a specified log label from matching log entries. Use filters to narrow down logs by host, path, service, or time range.

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
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, or workflow.
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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds that it calls GET /logs/values, but no extra behavioral context beyond what annotations imply. Minimal additional value.

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?

Two sentences, no fluff. Purpose is front-loaded. Every sentence is informative and necessary.

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 17 parameters and no output schema, the description is brief. It does not explain pagination, time range defaults, or ordering, which would help an agent. Schema covers parameters, but completeness is adequate but not excellent.

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 baseline is 3. Description does not add meaning beyond the schema; it only restates that it lists values for a given label. No extra parameter details.

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 the tool lists log label values for a given label with filters, clearly specifying the verb 'list' and resource 'log label values'. It differentiates from sibling tools like render_list_logs.

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?

No guidance on when to use this tool vs alternatives like render_list_logs or other list tools. Does not mention prerequisites or when-not-to-use.

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