Skip to main content
Glama
Sign In
reelsaw

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List projects

list_projects
Read-only

Lists your projects with the most recently updated first, paged via cursor, and can show only deleted projects still available to restore. Use it to browse and locate a project.

Instructions

Your projects, most recently updated first. Returns { projects: [{ id, title, status, stage, clips: "n/m rendered", url }], total, nextCursor }; pass nextCursor as cursor for the next page. deleted: true lists restorable deletes (storedBytes still count until purge_project). For every kind of restorable delete (projects, clips, library, templates) use list_deleted. Use get_project for one project's clips, search_clips to find by words.

Input Schema

NameRequiredDescriptionDefault
limitNoProjects per page (1-100, default 24)
cursorNonextCursor from the previous page; omit for the first page
deletedNotrue = only deleted projects that restore_project can still bring back

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / cursor / description
      Added value: +"nextCursor from the previous page; omit for the first page"
    • addedInput schema / properties / deleted
      Added value: +{
+  "description": "true = only deleted projects that restore_project can still bring back",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit / description
      Added value: +"Projects per page (1-100, default 24)"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With readOnlyHint already declaring safety, the description still adds real behavior: result ordering, the exact response envelope, the nextCursor pagination loop, and that deleted items' storedBytes still count until purge_project. That last point is non-obvious mutation-adjacent context an agent would otherwise miss.

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?

Densely packed, front-loaded with scope and ordering, and every clause carries information (response shape, pagination, deleted semantics, alternatives). It is a single long block rather than broken up, and the return-shape serialization is slightly verbose, but nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description supplies the full response envelope, pagination mechanics, deleted-mode caveat, and sibling disambiguation. For a three-param read-only list tool, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns extra: it explains that nextCursor must be passed as cursor for the next page (the pagination idiom) and clarifies what deleted:true really means (restorable deletes whose bytes still bill). It adds marginal but useful meaning beyond the schema strings.

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?

States the resource ('Your projects') and ordering ('most recently updated first') and implicitly the list verb, while naming the siblings it is not (get_project for a single project, search_clips for word search, list_deleted for other delete kinds). An agent can distinguish it from every sibling without opening a schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Use get_project for one project's clips, search_clips to find by words', and 'For every kind of restorable delete (projects, clips, library, templates) use list_deleted'. That covers when to use this versus alternatives, including the subtlety that deleted=true only lists projects.

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