Skip to main content
Glama

List a project's shorts

list_shorts
Read-onlyIdempotent

The project's shorts, each checked against the current long edit: text, ends, trims, title, layout, camera_focus, its own end card cta and website (null when it uses the brand kit's), the long video's stills and graphics it shows (visuals.shown, with their times) and any it leaves out, with why (visuals.left_out), checks, and whether its draft and final still match it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "list_shorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom create_project

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral detail about the returned checks, visuals.shown versus visuals.left_out, null end-card CTA/website semantics, and draft/final match status.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is information-dense and avoids obvious filler, but it is a single long run-on sentence with many comma-separated return fields. It would be easier to parse if front-loaded and structured into shorter clauses.

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?

For a one-parameter read-only list tool with no output schema, the description sufficiently explains what is returned, including nested visual and check details. It does not cover ordering, pagination, or error behavior, but the core return contract is well described.

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%, with project_id clearly described as coming from create_project. The prose adds no further parameter semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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

Purpose4/5

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

The description names the resource precisely: a project's shorts, including the specific per-short data and checks returned. It is clear this is a retrieval tool for shorts belonging to one project, though it does not explicitly distinguish itself from suggest_shorts or render_short_from_project.

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?

The description explains the returned content but gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer that this is the tool for inspecting existing shorts rather than suggesting or rendering them.

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