Skip to main content
Glama
Sign In
content-engine-mcp

content-engine-mcp

by DevMandalia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

list_drafts

Lists all channel draft versions for a given seed, so you can review or compare drafts before approval-gated sending.

Instructions

List all channel draft versions for a seed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seed_id": "<seed_id>"
    },
    "name": "list_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
seed_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about ordering, pagination, permissions, or whether killed/approved drafts are included. "All ... versions" is the only behavioral signal, implying a history listing.

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?

A single, front-loaded sentence with no filler or redundancy. Every word contributes to the stated scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should explain what a draft version contains and how results are shaped, but it does not. For a read tool that returns a collection keyed by a seed, the return semantics are left entirely unspecified.

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?

Only one parameter, seed_id, with 0% schema description coverage; the phrase "for a seed" minimally confirms that seed_id is a seed identifier. It adds almost no format, source, or validation meaning beyond the schema property name.

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?

"List all channel draft versions for a seed" gives a specific verb (List), a specific resource (channel draft versions), and a scope (for a seed). An agent can distinguish it from get_draft or list_seeds, though it never explicitly contrasts with those siblings.

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

Usage Guidelines2/5

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

No guidance on when to call this versus get_draft, get_draft_kit, or list_seeds, and no prerequisites or exclusions. The agent must infer usage from the name and phrasing 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