Skip to main content
Glama

List productions

list_projects
Read-only

Lists the productions in the signed-in Aufilm account, with title, format, planning status and each production's access state (unlocked, free first production, or locked). Call this first when the user refers to a production by name, or to see what already exists before creating a new one.

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_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real context beyond that: results are scoped to the signed-in account only, and each production carries an access state with named values (unlocked, free first production, locked), which hints at account entitlement limits an agent should expect.

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 no filler: the first states what is listed and what comes back, the second states when to call it. The usage trigger is front-loaded in the imperative ("Call this first"), which is exactly what an agent needs to act on.

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?

With an output schema present, return structure needn't be explained, and the description covers purpose, scope and call ordering for a simple zero-parameter read. The only gap is whether the list is ever truncated or paginated for large accounts, which is left unstated.

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 zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly avoids inventing input options and instead spends its words on scope and returned content.

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?

"Lists the productions in the signed-in Aufilm account" gives a specific verb and resource, and the sentence continues with the exact fields returned (title, format, planning status, access state). This clearly separates it from the singular get_project sibling and from create_project without needing the schema.

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?

Two explicit triggers are given: "Call this first when the user refers to a production by name" and "to see what already exists before creating a new one." That establishes ordering relative to create_project, but there is no explicit when-not case (e.g., skip it when the project ID is already known).

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