Skip to main content
Glama

List organization audit logs

render_list_organization_audit_logs
Read-onlyIdempotent

Retrieve audit logs for a Render organization, with optional time range filtering and pagination controls.

Instructions

List organization audit logs. Retrieve audit logs for a specific organization with optional filtering and pagination. Calls GET /organizations/{orgId}/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).
orgIdYesThe unique identifier of the organization
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)
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 the tool as read-only, idempotent, and non-destructive. The description adds the API method and path, but does not disclose further behavioral traits like rate limits, error handling, or the nature of audit logs. With annotations present, this is minimally acceptable.

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 extremely concise: two sentences that front-load the main action and include the API call. No redundant information; every word adds value.

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 the well-documented schema and annotations, the description covers the essential purpose but lacks detail on pagination mechanics, return format, and time range semantics. It is adequate but could be more complete for a list endpoint.

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 all parameters are documented in the schema. The description does not add additional parameter meaning beyond what the schema provides. Baseline of 3 is appropriate.

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 the tool's purpose: listing/retrieving organization audit logs with optional filtering and pagination. It explicitly mentions the API endpoint, which adds specificity. However, it does not differentiate from sibling tools like render_list_owner_audit_logs, so a 5 is not warranted.

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 is provided on when to use this tool versus alternatives (e.g., owner audit logs). It also lacks prerequisites or context for appropriate use. The description only states the action without any usage context.

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