Skip to main content
Glama

List projects

render_list_projects
Read-onlyIdempotent

Retrieve a filtered list of Render projects. Supports filtering by name, owner, creation or update time, and pagination.

Instructions

List projects. List projects matching the provided filters. If no filters are provided, all projects are returned. Calls GET /projects 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).
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)
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?

Annotations already declare readOnly, idempotent, non-destructive. Description adds the API call detail and no-filter behavior, but no new behavioral traits beyond 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?

Concise with three short sentences, though slightly repetitive ('List projects' appears twice). Efficient overall.

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?

No output schema; description does not specify return structure. While implied by name, 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 coverage is 100%, so baseline is 3. Description does not elaborate on parameter usage beyond what schema provides, only mentions 'matching filters' generically.

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 the tool lists projects and describes filtering behavior. Distinguishes from sibling tools like render_retrieve_project and other list tools.

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 says to use for listing projects with optional filters. Does not mention alternatives but context makes it clear.

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