Skip to main content
Glama
Sign In
mcp-sac-tools

mcp-sac-tools

by pmankineni
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

sac_export_story_start

Initiate an export job for a story (or other resource type) via Content Network. Returns a job ID to track status and download the package.

Instructions

Start a Content Network export job for a story (or other resource type). Returns the jobId. Use sac_export_status to poll until COMPLETED, then sac_export_download to fetch the package.

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": "sac_export_story_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
storyIdYesThe story ID (resource ID) to export
resourceTypeNoResource type — default 'story'. Use this for non-story exports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Discloses that it starts an export job and returns a jobId, but omits permissions, side effects, rate limits, or error conditions. Minimal behavioral context.

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?

Two sentences, no redundant information. Efficient and to the point.

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?

Explains return value (jobId) and workflow with sibling tools. No output schema needed. Lacks details on error handling or prerequisites, but adequate for a simple start-job tool.

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 schema already fully describes both parameters. Description adds value by hinting 'Use this for non-story exports' for resourceType, but does not add critical extra meaning beyond schema.

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 it starts a Content Network export job for a story or other resource type, returns jobId. Clearly distinguishes from sibling tools like sac_export_status and sac_export_download.

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?

Explicitly instructs to poll with sac_export_status and then fetch with sac_export_download, providing a clear workflow. Lacks explicit exclusions or when-not-to-use scenarios.

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