Skip to main content
Glama

List your private renders

list_renders
Read-onlyIdempotent

List the user’s private render projects: title, number of versions, latest video and the address of each project on Launchscene. Use a project id with save_render to add the next version.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_renders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing scope (the caller's own private projects only, i.e. per-user, auth-bound results) and by naming the fields returned and how the ids are consumed elsewhere. It does not state ordering, result limits, or behavior when the user has no projects.

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, zero waste, front-loaded with the action and scope, then the returned fields, then the follow-up workflow. Nothing is repeated from the annotations or title.

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?

An output schema exists, so return structure is already documented, and the description reinforces it with a short field list; the zero-parameter schema needs no explanation. What is missing is minor but real: whether all projects are returned or truncated, and in what order, which matters for a list tool that accepts no paging arguments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4 and there is no schema semantics for the description to supplement. The description correctly spends its words on scope and return content instead of inventing filter syntax the schema does not support.

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 opens with a specific verb and resource ('List the user's private render projects') and immediately enumerates the returned fields (title, version count, latest video, project address). The 'private' scope plus 'render projects' cleanly separates it from sibling list_* tools that cover boards, brands, or formulas.

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?

It tells the agent when the output is useful downstream: take a project id and pass it to save_render to add a new version. That is a concrete workflow pointer rather than vague framing. It stops short of explicit exclusions (e.g., 'use get_render_result for a single render's status'), so it is strong but not a full when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources