Skip to main content
Glama

List projects

list_projects
Read-onlyIdempotent

List your VoxTale projects, newest first, with titles. Use first when the user mentions their project, video or saved script by name or topic, then get_project for its material. Follow nextCursor, including after an empty filtered page. Does not search public content.

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
limitNo
queryNo
cursorNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
nextCursorYes

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 readOnly, idempotent, non-destructive and closed-world, so the description focuses on what annotations cannot convey: result ordering, the need to follow nextCursor, and the non-obvious case of continuing pagination after an empty filtered page. It stops short of describing result shape or limits, which is acceptable given the output schema exists.

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?

Four short sentences, front-loaded with what is returned and when to call it, with no filler. The pagination sentence is dense but each clause carries distinct operational value.

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?

For a three-parameter read-only list tool with an output schema, the description covers ordering, filtering intent, pagination continuation semantics and scope boundaries. Nothing an agent needs to invoke it correctly or handle the empty-page edge case is missing.

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 0%, so the description must carry parameter meaning. It explains the cursor parameter via "Follow nextCursor" and implies query filtering through "by name or topic" and "empty filtered page", but says nothing about the limit parameter or the maximum of 50, leaving one of three parameters undocumented.

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 and resource ("List your VoxTale projects") plus ordering ("newest first") and returned field ("with titles"). It also rules out a scope ("Does not search public content") and points to the complementary get_project, so an agent can separate it from siblings 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?

Gives an explicit triggering condition — "Use first when the user mentions their project, video or saved script by name or topic" — and names the follow-up tool (get_project) along with the reason to switch ("for its material"). The exclusion of public-content search adds a clear when-not.

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