Skip to main content
Glama

List carousels and download links

list_carousels
Read-only

Recent carousels of the account's catalog, newest first, with render status, the hook and caption CartViral wrote and, when done, a zip download link and each slide's Instagram/TikTok image links.

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_carousels"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already mark this as read-only. The description adds newest-first ordering, a scope of recent items, and the fact that download links appear only once rendering is done. It also describes the returned fields, which matters because there is no output schema.

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 dense sentence that packs in ordering, status and output contents. It is efficient but somewhat run-on, and it opens with a noun phrase rather than a verb.

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 simple one-parameter read tool with no output schema, it explains the return contents well. Minor gaps are the undocumented limit parameter and the lack of any note on pagination or what counts as 'recent'.

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%. The one parameter, 'limit', is never mentioned in the description, though 'recent' and the schema bounds (1-50, default 12) make its meaning inferable.

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?

It clearly lists recent carousels for the account's catalog and says what each entry contains: render status, hook, caption, zip link and per-slide image links. It does not set itself apart from list_creations, a sibling that could overlap.

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

Usage Guidelines3/5

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

Mentioning render status and download links implies its use after generate_carousel to check progress and get assets. It never says so outright, and it gives no when-not-to-use guidance or comparison with list_creations.

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.