Skip to main content
Glama

List Redis instances

render_list_redis
Read-onlyIdempotent

List Redis instances by name, region, owner, or creation time. Returns all instances when no filters are provided.

Instructions

[DEPRECATED by Render] List Redis instances. List Redis instances matching the provided filters. If no filters are provided, all Redis instances are returned. This API is deprecated in favor of the Key Value API. Calls GET /redis on the Render Public API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by name
limitNoThe maximum number of 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).
regionNoFilter by resource region
ownerIdNoThe ID of the workspaces to return resources for
createdAfterNoFilter for resources created after a certain time (specified as an ISO 8601 timestamp)
updatedAfterNoFilter for resources updated after a certain time (specified as an ISO 8601 timestamp)
createdBeforeNoFilter for resources created before a certain time (specified as an ISO 8601 timestamp)
environmentIdNoFilter for resources that belong to an environment
updatedBeforeNoFilter for resources updated before a certain time (specified as an ISO 8601 timestamp)
Behavior3/5

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

Description adds deprecation note but no behavioral details beyond annotations (readOnly, idempotent, etc.). Consistent 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with deprecation, no waste.

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?

Covers filtering and deprecation. No output schema, but pagination is in schema. Missing return format info, but acceptable.

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 coverage 100% with parameter descriptions. Description does not add meaning beyond 'matching provided filters'.

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?

Clearly states 'List Redis instances' with filtering and all/filtered behavior. Distinct from siblings like create, update, delete, retrieve.

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

Usage Guidelines4/5

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

Explicitly mentions deprecation in favor of Key Value API, advising when not to use. However, no direct alternative tool named.

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