Skip to main content
Glama

Export Product Suite Prompts

export_product_suite_prompts
Read-onlyIdempotent

Exports a product suite's validated prompts, unified style summary, and execution config read-only, so you can review current or historical versions without changing versions or generating images.

Instructions

只读重新导出整套的已校验提示词、统一风格摘要和实际执行配置;不改版本、不确认、不出图。

默认当前版,可查看历史版;历史版不能用于当前提交。与实际执行共用DrawingPrompt/ImageTask校验和编译器。 prompts.task给出商品冻结图及SHA256、三模型实际选档、接口与分类型画幅;不得绕过确认/收费流程直接回填通用出图入口。

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": {
      "design_id": "<design_id>"
    },
    "name": "export_product_suite_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionNo
design_idYes

Output Schema

NameRequiredDescriptionDefault
designYes
promptsYes
style_digestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds concrete substance: it clarifies that 'read-only' means no version change, no confirmation, no image output, that it shares DrawingPrompt/ImageTask validation and compiler with real execution, and warns against bypassing the confirmation/billing flow. These are meaningful behavioral constraints beyond the annotations.

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?

The read-only purpose and the primary negative constraints are front-loaded, followed by version-selection and validation-sharing detail. Dense with domain jargon (DrawingPrompt/ImageTask) but every sentence carries behavioral information; no filler.

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?

An output schema exists, so return structure need not be spelled out, yet the description still describes prompts.task contents (frozen image + SHA256, three-model selection, per-type frame sizes). For a domain-specific tool this is close to complete; only the design_id semantics and an explicit sibling comparison are missing.

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 description coverage is 0%, so the description must carry the burden. It partially does: 'defaults to current version, can view historical versions; historical versions cannot be used for current submission' explains the revision parameter's semantics well. The required design_id is left entirely unexplained, so coverage is incomplete.

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+resource: 'read-only re-export of the entire set of validated prompts, unified style summary, and execution configuration.' It also carves out scope by declaring what it does NOT do (no version change, no confirm, no image generation), which helps separate it from build_product_suite_prompts and the image-generation siblings. It stops short of naming an explicit sibling alternative, so not a 5.

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?

'Defaults to current version, can view historical versions; historical versions cannot be used for current submission' gives real guidance tied to the revision parameter and the submission flow. However, it never states when to reach for this tool versus build_product_suite_prompts or export_validated_reference_replica, so usage relative to siblings is only implied.

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