Skip to main content
Glama

Create outreach workflow

spur_create_workflow

Create a multi-step outreach sequence from saved templates. It's saved as an inactive draft: nothing sends until it's activated (spur_set_workflow_active) and owners are enrolled.

Send steps take a saved template: email/SMS from spur_list_message_templates (design new ones with spur_create_email_template / spur_create_sms_template), direct mail from the user's saved postcard or letter templates. Wait steps space them out. Add reply/open/click/scan branches and edit timing afterwards with spur_edit_workflow.

Example: "text, wait 2 days, email, wait 5 days, postcard" -> steps=[{type:"send_sms",template_id:…},{type:"wait",days:2},{type:"send_email",template_id:…},{type:"wait",days:5},{type:"send_direct_mail",template_id:…}]

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": {
      "name": "<name>",
      "steps": "<steps>"
    },
    "name": "spur_create_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesWorkflow name shown in Spur
stepsYesSteps in run order: send_email / send_sms / send_direct_mail with a saved template_id, and wait steps (days, hours) between them
descriptionNoOptional note about the workflow's goal

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, but the description adds the crucial behavioral fact that the workflow is an inactive draft and no outreach occurs until a separate activation step. It does not say what is returned on success (no output schema) or what happens on duplicate names, which keeps it from a 5.

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-loaded with purpose, then draft/activation semantics, then per-step-type guidance, then a worked example. Dense with parenthetical sibling references but each earns its place; the example is long yet directly reduces invocation errors.

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 nested, polymorphic steps array and no output schema, the description covers step types, template sourcing, ordering, pacing, and post-creation editing. It leaves out the return value and the max-30-step constraint (schema-only), but an agent has enough to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds meaning by explaining that send steps require a saved template_id and where those IDs come from, and that wait steps are the pacing mechanism between sends. The concrete example mapping a plain-English sequence onto the steps array gives real construction guidance 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?

Opens with a specific verb and resource: 'Create a multi-step outreach sequence from saved templates.' It also implicitly separates itself from the editing sibling ('edit timing afterwards with spur_edit_workflow') and from activation ('spur_set_workflow_active'), so an agent can route correctly without opening other schemas.

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 states the creation is a draft and that nothing sends until activation plus enrollment, naming the exact sibling that performs activation. It also routes the agent to the correct template sources (spur_list_message_templates, spur_create_email_template, spur_create_sms_template, postcard/letter lists) depending on step type.

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