GovTribe

Test run automation MCP tool

Start a manual test run for an existing GovTribe AI automation and return the started conversation, including a GovTribe URL when a conversation is available.

Examples

Use this tool to start a manual run against an existing automation. Supply only the extra context IDs that the automation's trigger type needs.

Start a manual run for a scheduled automation

{
  "tool": "Search_Automations",
  "arguments": {
    "query": "\"Weekly capture recap\"",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "trigger_details"
    ],
    "past_runs_limit": 0
  }
}
{
  "tool": "Test_Run_Automation",
  "arguments": {
    "workflow_id": "<automation_govtribe_id>"
  }
}

Start a saved-search test run with only five result rows

{
  "tool": "Test_Run_Automation",
  "arguments": {
    "workflow_id": "<automation_govtribe_id>",
    "saved_search_result_limit": 5
  }
}

Start a stage-change test run with explicit pipeline and stage context

{
  "tool": "Test_Run_Automation",
  "arguments": {
    "workflow_id": "<automation_govtribe_id>",
    "pipeline_id": "<pipeline_govtribe_id>",
    "stage_id": "<stage_govtribe_id>"
  }
}

Payload patterns

Always send workflow_id. Add pursuit_id, pipeline_id, or stage_id only when the automation's trigger needs extra runtime context for the manual test. Use saved_search_result_limit only for saved-search test runs.

{
  "tool": "Test_Run_Automation",
  "arguments": {
    "workflow_id": "<automation_govtribe_id>",
    "pipeline_id": "<pipeline_govtribe_id>",
    "stage_id": "<stage_govtribe_id>",
    "saved_search_result_limit": 5
  }
}