Skip to main content
Glama

list_story_drafts

Retrieve a story's saved drafts in newest-first order to review or resume writing. Specify the story ID and optionally limit how many drafts are returned.

Instructions

스토리의 임시저장 목록 (최신순).

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": {
      "storyId": "<storyId>"
    },
    "name": "list_story_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
storyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses only the sort order (newest first); nothing about read-only nature, permissions required to view drafts, pagination behavior, or what happens when a story has no drafts.

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

Conciseness3/5

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

A single short phrase with no padding, but it is under-specified rather than concise — the ordering detail is front-loaded, yet the sentence does not establish what is returned.

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?

No output schema and no annotations, with both parameters undocumented in the schema and ignored by the description. For a list tool whose result shape matters (IDs only vs. content previews), this leaves the agent guessing.

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

Parameters2/5

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

Schema description coverage is 0% and the description mentions neither storyId (required) nor limit (default 10, max 40). '최신순' hints at ordering but does not explain whether limit truncates the newest entries or how many drafts exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase '스토리의 임시저장 목록' identifies the resource (draft saves of a story) and implies a list operation, plus a newest-first ordering. It does not distinguish itself from the sibling get_story_draft, so an agent cannot tell from the text alone whether this returns full content or only entries.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites, and no comparison to get_story or get_story_draft which could plausibly overlap. The agent has to infer scope entirely.

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