Skip to main content
Glama

AgentPMT - Marketplace For Autonomous Agents

AgentPMT Workflow Creator

AgentPMT-Workflow-Creator

AgentPMT Workflow Creator - Build and manage multi-step AI agent workflows (skill chains) that orchestrate tools, prompts, loops, and human notifications into reusable DAG pipelines. Supports creating, updating, publishing, remixing, searching, and adding showcase examples to workflows. Access a catalog of 170+ tools to chain together. Call get_instructions before starting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoWorkflow skill name
skipNoNumber of results to skip for pagination
edgesNoWorkflow graph edges - array with {id, from, to, condition, sourceHandle?, targetHandle?}
limitNoMaximum results to return (1-200)
nodesNoWorkflow graph nodes - array of SkillChainNode objects
queryNoSearch query over name/description (case-insensitive)
actionYesThe action to perform
sort_byNoSort order for fetch_tools browse (no search query). 'recently_updated' or 'name'.recently_updated
skill_idNoSkill chain ObjectId or slug (required for update, publish, remix, delete; optional for fetch)
publisherNoFilter by publisher username (case-insensitive substring match, for search_public)
categoriesNoComma-separated category names to filter by (for search_public)
chat_modelNoOverride the workflow's chat model identifier. Must reference chat_model_config.available_models; null or blank clears the override on update.
version_idNoWorkflow version ObjectId for get_version and restore_version.
visibilityNoVisibility: private or public
descriptionNoWorkflow skill description
tool_searchNoSearch query for tools in fetch_tools action
version_bumpNoVersion bump type for publish: major, minor, patch, or auto
industry_tagsNoList of industry tag names to associate with this workflow
mcp_server_nameNoMCP server name (default: agentpmt)
validation_modeNoValidation mode for validate action. Defaults to agent_write.agent_write
showcase_exampleNoSingle showcase example to add (for add_showcase_example action)
checkpoint_reasonNoAutosave checkpoint reason.
time_saved_minutesNoEstimated minutes saved (>= 0)
context_document_idNoAgent Context document ObjectId for attach_context/detach_context.
showcase_example_idNoShowcase example id to remove (for remove_showcase_example action)
context_document_idsNoAgent Context document ObjectIds to attach to the workflow (max enforced by the agent_context domain). Replaces the existing set when provided.
industry_tags_filterNoComma-separated industry tag names to filter by (for search_public)
default_export_targetNoDefault export target: mcp or rest
exclude_private_toolsNoIf true, omit private tools from fetch_tools results
remixed_from_skill_idNoSource skill ID when creating a remix
include_published_onlyNoFor fetch_existing: only return skills that have been published
expected_draft_revisionNoRequired optimistic concurrency token for update, publish, delete, attach/detach, showcase, and restore actions.
remixed_from_skill_nameNoSource skill name when creating a remix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add_showcase_example",
      -  "attach_context",
      -  "create_new",
      -  "delete",
      -  "detach_context",
      -  "fetch_existing",
      -  "fetch_industry_tags",
      -  "fetch_tools",
      -  "get_instructions",
      -  "publish",
      -  "remix",
      -  "remove_showcase_example",
      -  "search_public",
      -  "update_existing",
      -  "validate"
      -]New value: +[
      +  "add_showcase_example",
      +  "attach_context",
      +  "checkpoint",
      +  "create_new",
      +  "delete",
      +  "detach_context",
      +  "fetch_existing",
      +  "fetch_industry_tags",
      +  "fetch_tools",
      +  "get_instructions",
      +  "get_version",
      +  "list_versions",
      +  "publish",
      +  "remix",
      +  "remove_showcase_example",
      +  "restore_published",
      +  "restore_version",
      +  "search_public",
      +  "update_existing",
      +  "validate"
      +]
    • addedInput schema / properties / checkpoint_reason
      Added value: +{
      +  "default": null,
      +  "description": "Autosave checkpoint reason.",
      +  "enum": [
      +    "idle",
      +    "window_blur",
      +    "visibility_hidden"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / expected_draft_revision
      Added value: +{
      +  "default": null,
      +  "description": "Required optimistic concurrency token for update, publish, delete, attach/detach, showcase, and restore actions.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / version_id
      Added value: +{
      +  "default": null,
      +  "description": "Workflow version ObjectId for get_version and restore_version.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "context_document_id"
      -]New value: +[
      +  "action"
      +]
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "action"
      -]New value: +[
      +  "action",
      +  "context_document_id"
      +]
  4. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "context_document_id"
      -]New value: +[
      +  "action"
      +]
  5. Changed28 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add_showcase_example",
      -  "create_new",
      -  "delete",
      -  "fetch_existing",
      -  "fetch_industry_tags",
      -  "fetch_tools",
      -  "get_instructions",
      -  "publish",
      -  "remix",
      -  "remove_showcase_example",
      -  "search_public",
      -  "update_existing",
      -  "validate"
      -]New value: +[
      +  "add_showcase_example",
      +  "attach_context",
      +  "create_new",
      +  "delete",
      +  "detach_context",
      +  "fetch_existing",
      +  "fetch_industry_tags",
      +  "fetch_tools",
      +  "get_instructions",
      +  "publish",
      +  "remix",
      +  "remove_showcase_example",
      +  "search_public",
      +  "update_existing",
      +  "validate"
      +]
    • addedInput schema / properties / categories / default
      Added value: +null
    • addedInput schema / properties / chat_model
      Added value: +{
      +  "default": null,
      +  "description": "Override the workflow's chat model identifier. Must reference chat_model_config.available_models; null or blank clears the override on update.",
      +  "type": "string"
      +}
    • addedInput schema / properties / context_document_id
      Added value: +{
      +  "default": null,
      +  "description": "Agent Context document ObjectId for attach_context/detach_context.",
      +  "type": "string"
      +}
    • addedInput schema / properties / context_document_ids
      Added value: +{
      +  "default": null,
      +  "description": "Agent Context document ObjectIds to attach to the workflow (max enforced by the agent_context domain). Replaces the existing set when provided.",
      +  "items": {
      +    "description": "",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / default_export_target / default
      Added value: +null
    • addedInput schema / properties / description / default
      Added value: +null
    • addedInput schema / properties / edges / default
      Added value: +null
    • addedInput schema / properties / exclude_private_tools / default
      Added value: +false
    • addedInput schema / properties / include_published_only / default
      Added value: +false
    • addedInput schema / properties / industry_tags / default
      Added value: +null
    • addedInput schema / properties / industry_tags_filter / default
      Added value: +null
    • addedInput schema / properties / mcp_server_name / default
      Added value: +null
    • addedInput schema / properties / name / default
      Added value: +null
    • addedInput schema / properties / nodes / default
      Added value: +null
    • addedInput schema / properties / publisher / default
      Added value: +null
    • addedInput schema / properties / query / default
      Added value: +null
    • addedInput schema / properties / remixed_from_skill_id / default
      Added value: +null
    • addedInput schema / properties / remixed_from_skill_name / default
      Added value: +null
    • addedInput schema / properties / showcase_example / default
      Added value: +null
    • addedInput schema / properties / showcase_example_id / default
      Added value: +null
    • addedInput schema / properties / skill_id / default
      Added value: +null
    • addedInput schema / properties / skip / default
      Added value: +0
    • addedInput schema / properties / time_saved_minutes / default
      Added value: +null
    • addedInput schema / properties / tool_search / default
      Added value: +null
    • addedInput schema / properties / version_bump / default
      Added value: +null
    • addedInput schema / properties / visibility / default
      Added value: +null
    • changedInput schema / required
      Previous value: -[
      -  "action"
      -]New value: +[
      +  "action",
      +  "context_document_id"
      +]
  6. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  7. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add_showcase_example",
      -  "create_new",
      -  "delete",
      -  "fetch_existing",
      -  "fetch_industry_tags",
      -  "fetch_instructions",
      -  "fetch_tools",
      -  "get_instructions",
      -  "publish",
      -  "remix",
      -  "remove_showcase_example",
      -  "search_public",
      -  "update_existing"
      -]New value: +[
      +  "add_showcase_example",
      +  "create_new",
      +  "delete",
      +  "fetch_existing",
      +  "fetch_industry_tags",
      +  "fetch_tools",
      +  "get_instructions",
      +  "publish",
      +  "remix",
      +  "remove_showcase_example",
      +  "search_public",
      +  "update_existing",
      +  "validate"
      +]
    • addedInput schema / properties / validation_mode
      Added value: +{
      +  "default": "agent_write",
      +  "description": "Validation mode for validate action. Defaults to agent_write.",
      +  "enum": [
      +    "agent_write",
      +    "draft_structure",
      +    "publish_executable"
      +  ],
      +  "type": "string"
      +}
  8. Added

TDQS

B3.2/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 disclosure burden. Yet it is essentially a feature list—it does not disclose mutation side effects (delete, publish, restore are all destructive), permission/auth requirements, reversibility, or response shape. The only behavioral disclosure is the get_instructions prerequisite. For a tool that can delete and publish workflows, this is a meaningful gap.

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?

Three sentences with the core purpose front-loaded, followed by a compact capability list and a crucial usage directive. No filler or redundancy. It could trim the enumerated actions slightly, but for a tool with 20 actions and 33 params it remains appropriately sized.

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

Completeness3/5

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

For a highly complex tool (20 actions, 33 params, nested objects, no output schema, no annotations), the description gives a solid high-level overview but lacks action-level routing—an agent is left guessing which of the 20 actions fits a given request. The 'call get_instructions' directive partially compensates by deferring detail, but the description itself does not make the tool safely callable without that extra step.

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 100%, so the schema fully documents all 33 parameters with detailed descriptions. The description adds contextual framing (DAG, skill chains, tool catalog) that helps interpret complex params like nodes/edges, but it doesn't explain parameter interplay or action-specific requirements beyond what the schema already provides. Baseline 3 is appropriate.

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?

The description states a clear purpose: building/managing multi-step AI agent workflows (skill chains) as DAG pipelines. It names the resource (workflows), the actions (create, update, publish, remix, search, showcase), and differentiates from siblings by framing itself as the workflow builder/manager. It doesn't explicitly contrast with AgentPMT-Workflow-Skills, leaving some sibling differentiation to inference, so it falls just short of 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?

The description gives one actionable directive: 'Call get_instructions before starting,' which is a useful prerequisite hint for a complex 20-action tool. However, it provides no when-to-use vs when-not-to-use guidance and never names alternatives among the siblings (e.g., when to route to AgentPMT-Workflow-Skills vs this creator). Usage context is implied but not explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources