sigrix-mcp

Official

Overview Schema Source Related Servers Discussions Admin

update_draft

Update fields on a draft or listing returned for corrections, then submit for moderation. Adjust prompts, personas, or skills before a moderator reviews.

Instructions

Update fields on a draft (or a listing returned for corrections). fields is an object of the seller API's ItemUpdate fields — for a prompt: main_prompt, context, rules, when_responding, output_format and scenarios (a list of {user_input, assistant_response}); for a persona: main_prompt plus tone, tagline, greeting, behavioral_notes; for a skill: instructions, license, compatibility, allowed_tools, skill_metadata; for any: name, description, category, tags, price_cents, seo_title. Accepted keys, with the type each one takes: name (string), title (string), category (string), seo_title (string), price_cents (integer), currency (string), tags (string[]), setup_complexity (string), interaction_type (string), main_prompt (string), context (string), rules (string), when_responding (string), output_format (string), tone (string), tagline (string), greeting (string), avatar_url (string), behavioral_notes (string), instructions (string), license (string), compatibility (string), allowed_tools (string[]), skill_metadata (object), example_input (string), example_output (string), skill_refs (string[]), mcp_requirements (object[]), persona_ref (string), prompt_ref (string), workflow_demo_media_url (string), workflow_demo_caption (string), scenarios (object[]), persona_module_id (string), building_blocks (object), testing_state (object), routing_logic (string), fallback_instructions (string), output_format_rules (string), prompt_ids (string[]), prompt_entries (object[]), variables (object[]), platform_notes (object[]), platforms (string[]), system_refs (object[]), process (string), handoff_map (object), synthesizer (string), system_version (string), listing_mode (string), metadata (object). The answer carries the saved record and its publish_eligibility. A listing that is pending_review cannot be edited until a moderator returns it. Nothing goes live from this tool: a submitted listing enters Sigrix's moderation queue as pending_review and a moderator decides.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fields`	Yes
`item_id`	Yes
`item_type`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full transparency burden. It discloses the moderation consequence ('Nothing goes live from this tool... enters Sigrix's moderation queue as pending_review'), the edit-blocking pending_review rule, and the response content ('the saved record and its publish_eligibility'). It does not discuss authorization, failure modes, or overwrite semantics, but the core behavioral traits are conveyed.

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 description is front-loaded with purpose and then provides a dense but necessary field reference. The list of accepted keys is long and arguably could be simplified, but every section adds value given the zero-coverage schema. It is structured logically: purpose, field groupings, key/type list, then behavioral notes.

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 tool with a complex nested `fields` object and no schema descriptions, the description is thorough: it covers allowed keys, types, item-type variations, moderation behavior, and response shape. Minor gaps exist, such as explicit valid values for `item_type` and whether partial field updates are allowed, but the overall picture is complete enough for correct invocation.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates with an exhaustive list of accepted field keys and their types. It also explains how field applicability varies by item_type (prompt, persona, skill, any). This turns an opaque generic 'fields' object into a well-specified parameter.

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?

The description opens with a specific verb and resource: 'Update fields on a draft (or a listing returned for corrections).' It clearly distinguishes the tool from siblings by scoping it to drafts and moderated returns, and further elaborates the item types and field categories. An agent can immediately tell this is for editing existing draft state, not creating or submitting.

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?

The description gives clear context for when to use the tool (updating drafts or listings in correction state) and states an explicit exclusion: 'A listing that is pending_review cannot be edited until a moderator returns it.' It does not explicitly name sibling alternatives like create_draft or submit_for_review, but the usage boundary is well implied by the sibling set.

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

Deploy Server