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. On the MCP surface, always send the flattened trigger_type plus trigger_config shape.

Create a weekly capture recap

{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Capture Reviews",
    "name": "Weekly capture recap",
    "prompt": "Review recent opportunity activity, highlight the biggest capture changes, and draft a concise weekly recap for our team.",
    "trigger_type": "trigger-schedule",
    "trigger_config": {
      "rrule": "RRULE:FREQ=WEEKLY;BYDAY=MO;BYHOUR=9;BYMINUTE=15"
    }
  }
}

If you create a saved search only to trigger this automation, create it with frequency: "Never" so only the automation sends the user email. Do not change an existing saved search's frequency just because the automation should email the user.

{
  "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.",
    "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.",
    "trigger_type": "trigger-saved-search-results",
    "trigger_config": {
      "saved_search_model_id": "<saved_search_govtribe_id>"
    }
  }
}

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.",
    "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

Use the flat MCP boundary every time: top-level govtribe_ai_project_name, name, prompt, trigger_type, and trigger_config.

Inside trigger_config, send only the keys that match the chosen trigger_type. rrule is required for schedule automations. saved_search_model_id is required for saved-search triggers. stage_direction is required for pursuit-stage triggers, with optional pipeline_model_id and stage_model_id scoping.

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 the older nested trigger: { type, config } shape in new MCP calls. The server still tolerates it for older integrations, but the documented contract is flattened.

Do not send internal notification_node or notification_config payloads from MCP. Create_Automation accepts only the flat completion notification keys above.

{
  "tool": "Create_Automation",
  "arguments": {
    "govtribe_ai_project_name": "Automation project name",
    "name": "Automation name",
    "prompt": "Prompt text",
    "on_completion_notify_user": "always",
    "completion_notification_instructions": "Start with the highest-priority finding, then summarize the rest in bullets.",
    "trigger_type": "trigger-schedule",
    "trigger_config": {
      "rrule": "RRULE:FREQ=DAILY;BYHOUR=9;BYMINUTE=0",
      "rrule_timezone": "America/New_York"
    }
  }
}

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 weekly capture recapCreate an automation from a saved searchCreate a stage-change automation for one pipeline stagePayload patternsRelated articles