easysociable-mcp

List slideshow runs

list_slideshow_runs

Read-onlyIdempotent

List and filter slideshow runs by platform, status, or search query to find run IDs for inspection, updates, or archiving. Returns run metadata, page counts, revisions, and timestamps.

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.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search term matching run title, topic, or content text.
`status`	No	Lifecycle status filter: draft \| active \| archived \| trash
`brandId`	No	Filter runs styled with a specific Brand ID.
`platform`	No	Target platform filter: tiktok \| linkedin \| instagram \| threads \| xiaohongshu
`profileId`	No	Optional profile filter.
`contentSlug`	No	Filter runs generated from a specific content topic slug.
`brandProfileId`	No	Optional legacy brand profile filter.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`runs`	No	Array of slideshow run summary items.
`total`	No	Total count of matching runs.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

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

Changed7 schema fields changedv0.1.16Oct 5, 2026

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"

First observedv0.1.13Oct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: the result set is scoped to the authenticated workspace owner, and it enumerates the returned fields (metadata, platform target, page counts, revision numbers, timestamps). It stops short of pagination/limit behavior, keeping it just under a 5.

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

Conciseness5/5

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

Front-loaded with the core action, then labeled 'Alternatives:' and 'Behavior:' segments that make scanning easy. Every sentence carries distinct information with no redundancy.

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?

An output schema exists, so return values needn't be spelled out, yet the description still names the key fields. Combined with clear usage routing and safety context, nothing an agent needs to invoke this correctly 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 100%, so all seven filters are already documented in the schema, and the description only summarizes three of them (platform, status, query). Baseline 3 is correct since the schema does the heavy lifting and the description adds no syntax or format detail beyond it.

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') with the scoping constraint and filter categories front-loaded. It explicitly distinguishes itself from get_slideshow_run, so an agent can tell them apart without opening either 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?

Names concrete use cases ('browse existing carousels or find a runId before inspection, updating, or archiving') and an explicit alternative with its selecting condition ('Use get_slideshow_run when you already have a specific runId'). Nothing is left to inference.

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