Skip to main content
Glama

List slideshow runs

list_slideshow_runs
Read-onlyIdempotent

Browse and filter owner-scoped slideshow runs by platform, status, brand, or search query, then retrieve a runId for inspection, updates, or archiving.

Instructions

List owner-scoped Slideshow Runs with optional platform, lifecycle status, or search query filters. Returns run metadata, platform target, page counts, revision numbers, and timestamps. Call to browse existing carousels or find a runId before inspection, updating, or archiving. Alternatives: Use get_slideshow_run when you already have a specific runId to fetch full slide content. Behavior: Read-only query scoped to current authenticated workspace owner.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch term matching run title, topic, or content text.
statusNoLifecycle status filter: draft | active | archived | trash
brandIdNoFilter runs styled with a specific Brand ID.
platformNoTarget platform filter: tiktok | linkedin | instagram | threads | xiaohongshu | x
profileIdNoOptional profile filter.
contentSlugNoFilter runs generated from a specific content topic slug.
brandProfileIdNoOptional legacy brand profile filter.

Output Schema

NameRequiredDescriptionDefault
runsNoArray of slideshow run summary items.
totalNoTotal count of matching runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.46
    • changedInput schema / properties / platform / description
      Previous value: -"Target platform filter: tiktok | linkedin | instagram | threads | xiaohongshu"New value: +"Target platform filter: tiktok | linkedin | instagram | threads | xiaohongshu | x"
  2. Changed1 schema field changedv0.1.17
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "runs": {
      +      "description": "Array of slideshow run summary items.",
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Total count of matching runs.",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed7 schema fields changedv0.1.16
    • addedInput schema / properties / brandId
      Added value: +{
      +  "description": "Filter runs styled with a specific Brand ID.",
      +  "type": "string"
      +}
    • addedInput schema / properties / brandProfileId / description
      Added value: +"Optional legacy brand profile filter."
    • addedInput schema / properties / contentSlug / description
      Added value: +"Filter runs generated from a specific content topic slug."
    • addedInput schema / properties / platform / description
      Added value: +"Target platform filter: tiktok | linkedin | instagram | threads | xiaohongshu"
    • addedInput schema / properties / profileId / description
      Added value: +"Optional profile filter."
    • addedInput schema / properties / q / description
      Added value: +"Search term matching run title, topic, or content text."
    • addedInput schema / properties / status / description
      Added value: +"Lifecycle status filter: draft | active | archived | trash"
  4. First observedv0.1.13

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world; the description adds the meaningful scoping fact that results are limited to the current authenticated workspace owner, which is not in the annotations. It does not discuss pagination or result limits, so it is strong but not exhaustive.

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?

Front-loads purpose, then usage, then alternatives, then behavior in a logical order with no wasted clauses. The 'Returns run metadata, platform target, page counts, revision numbers, and timestamps' sentence partly duplicates the output schema, costing a little density.

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?

Seven optional parameters, full schema coverage, an output schema and rich annotations mean the description only needs to supply scope and routing guidance, which it does. Pagination/result-size behavior is the remaining gap for a list tool.

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 all seven parameters are already documented, and the description only gestures at three filter families (platform, status, search). That matches the baseline for a fully documented schema without adding filter-combination or default semantics.

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 owner-scoped Slideshow Runs') plus the filter set, and explicitly contrasts with get_slideshow_run so the agent can distinguish the two 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 a concrete use case ('browse existing carousels or find a runId before inspection, updating, or archiving') and names the alternative tool plus the condition that selects it ('when you already have a specific runId').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.