Skip to main content
Glama
Sign In
reels

reels

by Endroe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reels_list

Read-only

Lists projects with compact summaries and pagination to help you browse and choose the project to edit or render.

Instructions

List projects with compact summaries and pagination.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already establish that this is a safe read-only, non-destructive, closed-world operation, so the description carries a lighter burden. It adds that results are compact summaries and paginated, but does not explain the default page size, the 50-item cap, or what a summary omits, which matters for a listing tool.

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?

A single front-loaded sentence with no filler and no repetition of the title. It is terse but not padded; the shortfall is missing content rather than excess wording.

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

Completeness2/5

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

With no output schema, two undocumented parameters, and a large ambiguous sibling set, the description is not complete enough. It never clarifies what a 'project' is in this domain, what fields a compact summary includes, or how to page through results.

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

Parameters2/5

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

Schema description coverage is 0% for the two parameters, so the description must compensate and largely fails. The word 'pagination' hints at limit/offset, but the defaults (20, 0) and the maximum limit of 50 are never mentioned, and 'offset' is not described in terms of units.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb (List) and a resource (projects) with a note on compact summaries and pagination. However, in a sibling set full of asset/shot/entity tools, it is unclear whether 'projects' is the correct resource for reels_list, and nothing distinguishes it from reels_catalog or reels_search_assets.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no reference to any alternative among the 20 sibling tools. An agent has to guess whether to call reels_list or reels_catalog first.

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