Skip to main content
Glama
osbytes

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List projects

list_projects
Read-only

Lists projects most recently updated first, with pagination, and returns each project's status, stage, clip render count, and URL.

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. Use get_project for one project's clips, search_clips to find by words.

Input Schema

TableJSON 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.5/5.0
Behavior4/5

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

readOnlyHint already covers the safety profile, so the description's added value is the sort order, the inline return shape (including the derived 'clips: n/m rendered' field), and the pagination contract. It does not mention rate limits or auth, but for a read-only list tool the disclosed behavior is substantive.

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?

Three tight clauses: identity/ordering, return shape + pagination, then sibling routing. Front-loaded and every sentence carries information an agent needs; nothing is padding.

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, but the description documents the return payload and cursor field anyway, and it covers ordering and next-page mechanics. Combined with a fully described parameter schema, an agent has everything needed to call and page through it.

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 description coverage is 100%, so limit, cursor, and deleted are already fully documented, including the restore_project link for deleted. The description only restates the cursor handoff, adding no meaning beyond the schema. Baseline 3 applies.

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 a specific verb+resource ('Your projects'), plus the ordering ('most recently updated first'), which immediately separates it from the mutating project siblings. It also names the two relevant alternatives (get_project, search_clips), so an agent can route 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?

Explicitly names alternatives with the condition that selects them: get_project for a single project's clips, search_clips for finding by words. Pagination guidance ('pass nextCursor as cursor for the next page') tells the agent exactly how to continue a multi-page call.

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