Skip to main content
Glama
Sign In
Modal MCP Server

Modal MCP Server

by IsaiahDupree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

modal_render_list

Retrieve recent Modal render jobs from Supabase with status, URLs, and render times. Filter by job state and limit results to track video rendering progress and access output links.

Instructions

List recent Modal render jobs from Supabase memory. Shows status, URL, render time, and label.

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": "modal_render_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax jobs to return (default: 20)
statusNoFilter by status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Adds valuable context about data source ('Supabase memory') and compensates for missing output schema by listing return fields (status, URL, render time, label). Missing: definition of 'recent' time window, pagination behavior, or read-only safety confirmation.

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 with zero waste. First sentence establishes operation and source; second sentence documents return values. No filler or redundant phrases.

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?

Adequately compensates for missing output schema by enumerating return fields. Parameters are simple and fully documented in schema. Minor gap: undefined time scope for 'recent' jobs.

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 has 100% description coverage ('Max jobs to return', 'Filter by status'), establishing baseline 3. Description does not add syntax details, format constraints, or examples beyond what schema provides.

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?

Clear verb ('List') and resource ('Modal render jobs') with specific data source ('Supabase memory'). Distinguishes from siblings modal_render (likely create) and modal_render_get (likely specific retrieval) through 'List recent', but does not explicitly name alternatives.

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

Usage Guidelines3/5

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

Implied usage through 'List recent' (browse history vs. specific lookup), but lacks explicit when-to-use guidance contrasting it with modal_render_get or modal_render. No prerequisites or exclusions stated.

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

Deploy Server

Other Tools