Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List folders

list_folders
Read-onlyIdempotent

List campaign, audience, or account folders; filter by parent ID to browse root or nested folder structures.

Instructions

List folders. Required API key scope: campaigns:read | audiences:read | accounts:read. GET /folders Required scope depends on type: CAMPAIGN → campaigns:read, AUDIENCE → audiences:read, ACCOUNT or omitted → accounts:read. Without type, folders of all types are returned. Returns root folders unless parentId is given.

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

Input Schema

NameRequiredDescriptionDefault
typeNo
parentIdNoParent folder id; `root` or omitted for root folders.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds genuinely useful context by spelling out required API key scopes per `type` value and the default return scope. It does not disclose pagination, ordering, or response shape, which an agent listing a potentially large collection would want.

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-loaded with purpose, endpoint, and defaults, then the per-type scope mapping. The scope requirement is stated twice (a summary line plus the per-type breakdown), which is slight duplication, though the second occurrence carries the type-specific nuance.

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?

With only two optional parameters, no output schema, and read-only annotations, the description covers what an agent needs: endpoint, auth scope per branch, and defaults for both parameters. Pagination would be a nice addition but is not essential to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% (the `type` enum has no description), and the description fully compensates by mapping each enum value to its required scope and stating that omission returns all types. It also reinforces `parentId` semantics with the 'root' default, matching and extending the schema's own description.

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 states a specific verb and resource ('List folders') and immediately clarifies scope: all types when `type` is omitted, root folders unless `parentId` is given. It does not distinguish itself from folder siblings like create_folder/update_folder/delete_folder, but the read-only listing purpose is unambiguous.

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

Usage Guidelines4/5

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

Clear operational context is provided: omitting `type` returns folders of all types, and omitting `parentId` returns root folders. What is missing is explicit routing to alternatives (e.g., use create_folder to create, update_folder to rename) — the agent must infer that from names alone.

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

Deploy Server

Other Tools