Skip to main content
Glama
Sign In
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Workflows: create

workflows_create

Create a new workflow with one trigger and no steps. Choose Manual, Timed, Event, or Api, then add steps and enable it when ready.

Instructions

Create a new workflow. Creates the workflow with one trigger and no steps: Manual needs entity, Timed needs cron, Event needs entity plus an event (EntityCreated by default) and an optional filter, and Api needs api_route. It stays disabled unless enabled is set; add steps with workflows_step_add, then turn it on with workflows_enable.

Input Schema

NameRequiredDescriptionDefault
cronNoCron expression, required for a Timed trigger (e.g. '0 9 * * *')
nameYesWorkflow name
eventNoEvent for an Event trigger: EntityCreated (default), EntityUpdated, EntityDeleted, UserRegistered, PaymentSucceeded and others. Not case-sensitive
entityNoEntity name, required for an Event or Manual trigger
filterNoFilter expression JSON for Event trigger (fires only when predicate matches the row)
enabledNoEnable workflow immediately after creation
triggerNoTrigger type: Manual (default), Timed, Event, Api. Not case-sensitive
api_routeNoAPI route, required for an Api trigger
descriptionNoWorkflow description
filter_fileNoPath to a file containing the filter expression JSON

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.37
    • changedInput schema / properties / api_route / description
      Previous value: -"Custom API route (for Api trigger)"New value: +"API route, required for an Api trigger"
    • changedInput schema / properties / cron / description
      Previous value: -"Cron expression (for Timed trigger, e.g. '0 9 * * *')"New value: +"Cron expression, required for a Timed trigger (e.g. '0 9 * * *')"
    • changedInput schema / properties / entity / description
      Previous value: -"Entity name for Event trigger"New value: +"Entity name, required for an Event or Manual trigger"
    • changedInput schema / properties / event / description
      Previous value: -"Event type: EntityCreated, EntityUpdated, EntityDeleted"New value: +"Event for an Event trigger: EntityCreated (default), EntityUpdated, EntityDeleted, UserRegistered, PaymentSucceeded and others. Not case-sensitive"
    • changedInput schema / properties / trigger / description
      Previous value: -"Trigger type: Manual, Timed, Event, Api"New value: +"Trigger type: Manual (default), Timed, Event, Api. Not case-sensitive"
  2. Addedv0.2.27

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare a non-read-only, non-destructive write, but the description adds crucial behavioral context: the workflow stays disabled unless enabled is set, it is created with exactly one trigger and zero steps, and each trigger type has specific parameter requirements. This goes well beyond the annotation set.

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?

Front-loads the core action and then packs trigger requirements, default state, and next steps into a single dense second sentence. It earns its length but the second sentence is run-on enough to benefit from slight restructuring.

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?

Covers the creation lifecycle well, including the disabled default and the follow-up steps. It does not explain how to reference the newly created workflow for subsequent steps (e.g., whether an ID is returned), a minor gap given there is no output schema.

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% and each parameter's schema description already documents its trigger-specific requirements and defaults. The description restates these conditions (e.g., 'Manual needs entity', 'Timed needs cron') but adds no new syntax or constraints beyond the 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 a specific verb and resource ('Create a new workflow') and immediately scopes it to a workflow with one trigger and no steps. It distinguishes itself from siblings by naming workflows_step_add and workflows_enable as the next steps in the lifecycle.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly covers when to use this tool (initial creation of a trigger-only workflow), what it cannot do (no steps), and names the alternative tools for adding steps and enabling. The trigger-type requirements further specify invocation conditions.

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