GovTribe
MCP tools

Create automation MCP tool

Create a GovTribe AI automation. Also creates a new GovTribe AI project with the given govtribe_ai_project_name to hold this automation.

Examples

Each call creates a fresh GovTribe AI project named govtribe_ai_project_name and links the new automation to it. Send one or more independent start triggers in start_nodes. Any one start node can run the same saved prompt.

Create a record-change monitor with a weekly backstop

This automation can run when the selected award changes OR on the weekly schedule. The record trigger watches only that exact award; the scheduled run gives the prompt a separate cadence for broader recompete research.

{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Recompete Watch",
    "name": "Award change and recompete monitor",
    "prompt": "Monitor award <award_govtribe_id> for modifications and lifecycle changes that affect recompete timing. On scheduled runs, also look for credible related follow-on signals and recommend only evidence-backed capture actions.",
    "reasoning_level": "low",
    "on_completion_notify_user": "conditionally",
    "completion_notification_instructions": "Email me only when a material award change or credible follow-on signal changes our capture timing or recommended action.",
    "start_nodes": [
      {
        "trigger_type": "trigger-entity-activity",
        "trigger_config": {
          "target_govtribe_type": "federal_contract_award",
          "target_govtribe_id": "<award_govtribe_id>"
        }
      },
      {
        "trigger_type": "trigger-schedule",
        "trigger_config": {
          "rrule": "RRULE:FREQ=WEEKLY;BYDAY=MO;BYHOUR=9;BYMINUTE=15",
          "rrule_timezone": "America/New_York"
        }
      }
    ]
  }
}

Saved-search email and automation polling are independent. You can leave the saved search's frequency unchanged or set it to Never; either choice leaves the automation trigger active. The automation's completion email is a third, separate setting.

{
  "tool": "Search_Saved_Searches",
  "arguments": {
    "query": "Healthcare IT recompetes",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "frequency"
    ]
  }
}
{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Healthcare Signals",
    "name": "Saved search result triage",
    "prompt": "Review the new saved-search matches, rank them for our capture team, and call out any records that need immediate follow-up.",
    "reasoning_level": "low",
    "on_completion_notify_user": "conditionally",
    "completion_notification_instructions": "Email me only when a new result looks like a priority pursuit. Keep the email short and start with the recommended action.",
    "start_nodes": [
      {
        "trigger_type": "trigger-saved-search-results",
        "trigger_config": {
          "saved_search_model_id": "<saved_search_govtribe_id>",
          "frequency": "daily"
        }
      }
    ]
  }
}

For MCP calls, frequency is required for every new saved-search trigger and accepts instant, daily, or weekly. Instant checks every 15 minutes. Choose the automation cadence explicitly; later changes to the saved search's email cadence are not copied to the automation. A new trigger begins listening when it is created and does not replay earlier matching results.

Create a stage-change automation for one pipeline stage

{
  "tool": "Search_Pipelines",
  "arguments": {
    "query": "Defense Health pipeline",
    "fields_to_return": [
      "govtribe_id",
      "name"
    ]
  }
}
{
  "tool": "Search_Stages",
  "arguments": {
    "query": "Proposal",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "pipeline"
    ]
  }
}
{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Proposal Changes",
    "name": "Proposal stage entry briefing",
    "prompt": "When a pursuit enters Proposal, explain what changed, summarize the likely work ahead, and recommend the next capture actions.",
    "reasoning_level": "low",
    "start_nodes": [
      {
        "trigger_type": "trigger-updated-pursuit-stage",
        "trigger_config": {
          "pipeline_model_id": "<pipeline_govtribe_id>",
          "stage_model_id": "<stage_govtribe_id>",
          "stage_direction": "enter"
        }
      }
    ]
  }
}

Payload patterns

start_nodes must contain at least one item. GovTribe preserves its order and returns a stable start_node_id for every created item. The triggers are independent OR starts, not conditions that must all match.

Trigger typeMatching trigger_config
trigger-scheduleRequired rrule; optional rrule_timezone, which defaults to America/New_York.
trigger-entity-activityRequired target_govtribe_type and target_govtribe_id for one exact supported government record. It fires after GovTribe records new activity for that record.
trigger-saved-search-resultsRequired saved_search_model_id and independent frequency: instant, daily, or weekly.
trigger-new-or-updated-pipelineOptional pipeline_model_id; omit it to use any accessible pipeline.
trigger-new-or-updated-pursuitOptional pipeline_model_id; omit it to use pursuits from any accessible pipeline.
trigger-updated-pursuit-stageRequired stage_direction with enter or exit; optional pipeline_model_id and stage_model_id.

trigger-entity-activity accepts these target_govtribe_type values:

  • federal_contract_award
  • federal_contract_idv
  • federal_contract_opportunity
  • federal_contract_vehicle_opportunity
  • federal_grant_opportunity
  • federal_grant_award
  • federal_forecast
  • state_local_contract_opportunity

Do not send the retired trigger_type, trigger_config, trigger, or triggers request shapes. Create accepts only start_nodes for start-trigger definitions.

A minimal scheduled automation uses the same array contract:

{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Automation project name",
    "name": "Daily review",
    "prompt": "Review material changes and recommend the next action.",
    "reasoning_level": "low",
    "start_nodes": [
      {
        "trigger_type": "trigger-schedule",
        "trigger_config": {
          "rrule": "RRULE:FREQ=DAILY;BYHOUR=9;BYMINUTE=0",
          "rrule_timezone": "America/New_York"
        }
      }
    ]
  }
}

Use the flat completion notification fields when the automation should email the authenticated user after future runs:

FieldNotes
on_completion_notify_userOptional. Use always, conditionally, or never. Omit it or set never when the automation should not send a completion email.
completion_notification_instructionsRequired with conditionally, optional with always, and ignored with never. Use it for the condition, formatting guidance, tone, or summary instructions.

Do not send internal notification_node or notification_config payloads from MCP.

Use reasoning_level to control how much deliberate reasoning each automation run uses:

ValueGood fit
noneMechanical scanning, extraction, or explicit rules with no meaningful judgment.
lowRoutine classification, summarization, and straightforward fit checks. Recommended for most automations.
mediumMulti-signal comparison, ambiguity resolution, or consequential recommendations.
highDifficult multi-step analysis, competing evidence, or substantial planning.

The field is optional on create and defaults to low. Choose the lowest level that can reliably complete the task. The stable values do not identify a particular AI model.

BLS occupational wage data

Query GSA CALC+ BLS occupational wage data either as normalized search rows or as aggregation-derived filter options for pricing workflows.

Create contact group

Create a GovTribe workspace contact group, optionally seeded with contacts and linked to a saved Contact search.

On this page

ExamplesCreate a record-change monitor with a weekly backstopCreate an automation from a saved searchCreate a stage-change automation for one pipeline stagePayload patternsRelated articles