Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List campaigns

list_campaigns
Read-onlyIdempotent

Retrieve SlideCold campaigns newest first, with optional filters to show only archived campaigns or campaigns in a specific folder.

Instructions

List campaigns. Required API key scope: campaigns:read. GET /campaigns Returns non-archived campaigns, newest first. With archived=true, returns only ARCHIVED campaigns (and folderId is ignored).

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

Input Schema

NameRequiredDescriptionDefault
archivedNo`true` to list only archived campaigns.
folderIdNoFolder id, or `root` for items not in any folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses the default result set (non-archived only), the ordering (newest first), the archived-mode override, and the auth scope requirement — meaningful behavioral context an agent could not infer from the annotations. It does not mention pagination or result-size limits, which is the main remaining gap for a list endpoint.

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 the core action and the auth/endpoint details, then the behavioral notes, with zero filler sentences. The opening "List campaigns." merely echoes the title, a minor redundancy in an otherwise tight definition.

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 two-parameter, read-only list tool with no output schema, the definition covers default filtering, ordering, the archived override, the folderId interaction, and required scope — enough to call it correctly. Only pagination/result-limit behavior is unaddressed, which keeps it short of a 5.

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 coverage is 100%, so the enum values and folderId meaning are already documented, which sets the baseline at 3. The description adds one genuinely new fact — that folderId is ignored when archived=true — but otherwise restates what the schema already says.

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?

States a specific verb and resource ("List campaigns") and adds the underlying endpoint GET /campaigns, so the operation is unambiguous and clearly distinct from get_campaign or create_campaign by name and scope. It stops short of explicitly contrasting itself with the single-campaign retrieval sibling, but the read-many semantics come through.

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?

The description implies usage through the archived flag semantics (archived=true returns only archived, folderId ignored) and names the required API key scope campaigns:read, which tells the agent it needs read credentials. However, it never states when to reach for this tool versus get_campaign or list_campaign_recipients, leaving the routing to the name 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