Skip to main content
Glama

List workspace audit logs

render_list_owner_audit_logs
Read-onlyIdempotent

Retrieve audit logs for a workspace with filtering by time range, pagination, and direction control.

Instructions

List workspace audit logs. Retrieve audit logs for a specific workspace with optional filtering and pagination. Calls GET /owners/{ownerId}/audit-logs on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoThe maximum number of audit log items to return. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
cursorNoThe position in the result list to start from when fetching paginated results. For details, see [Pagination](https://api-docs.render.com/reference/pagination).
endTimeNoEnd time for filtering audit logs (ISO 8601 format)
ownerIdYesThe ID of the workspace to return resources for
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
startTimeNoStart time for filtering audit logs (ISO 8601 format)
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, indicating a safe read operation. The description adds the API endpoint and confirms it is a retrieval. It does not disclose additional behavioral traits such as rate limits, potential empty results, or any side effects, but it does not contradict annotations.

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 two sentences long, front-loaded with the core purpose, and minimal. Every sentence adds value: the first states the action and resource, the second adds filtering/pagination and the API call. No wasted words.

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?

Given no output schema, the description could inform about the return format (e.g., a list of audit log entries) but does not. The tool is simple with well-described parameters, but the lack of output details reduces completeness. It is adequate but not fully comprehensive.

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 coverage is 100% with detailed descriptions for all 6 parameters. The description does not add extra meaning beyond stating 'optional filtering and pagination'; it relies on the schema. Therefore, the description does not significantly enhance parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List workspace audit logs' and explains it retrieves logs for a specific workspace with optional filtering and pagination. It references the API endpoint. While it distinguishes from sibling tools by specifying 'workspace' and using 'ownerId', it does not explicitly contrast with the sibling tool 'render_list_organization_audit_logs', which could be for organization-level 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?

The description provides basic usage ('Retrieve audit logs for a specific workspace with optional filtering and pagination') but offers no guidance on when to use this tool versus alternatives like 'render_list_organization_audit_logs' or 'render_list_logs'. There are no when-not-to-use indications or explicit context for selection.

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