Search automations MCP tool

• MCP tool name: Search_Automations
• Data type: Automation data type
• Returns: Automation MCP response
• Search modes: Keyword, Semantic
• Annotations: Read only, not destructive, idempotent, closed world
• Surfaces: GovTribe AI

Examples

Search returns only automations owned by the calling user. Archived automations do not appear. Use fields_to_return to request the automation fields you need, including reasoning_level, start_nodes, version_number, and completion email fields before an update.

start_nodes is the ordered, round-trippable trigger list. Search embeds up to three start nodes per automation by default and also returns total_triggers_count. Set max_triggers to a larger number when you need more; it has a minimum of one and no maximum. If the returned list is shorter than total_triggers_count, repeat the search with a larger value before editing or test-running a trigger that is not yet loaded.

trigger_details remains available as a compatibility snapshot of the first start node only. Do not use it to inspect or edit every trigger on a multi-trigger automation.

Which automations mention recompete monitoring?

{
  "tool": "Search_Automations",
  "arguments": {
    "query": "recompete monitoring for expiring contracts",
    "search_mode": "semantic",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "govtribe_ai_project_name",
      "reasoning_level",
      "state",
      "updated_at"
    ]
  }
}

Load the current version and start triggers before editing

{
  "tool": "Search_Automations",
  "arguments": {
    "query": "\"Award change and recompete monitor\"",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "reasoning_level",
      "version_number",
      "start_nodes",
      "total_triggers_count",
      "on_completion_notify_user",
      "completion_notification_instructions"
    ],
    "max_triggers": 50,
    "past_runs_limit": 0
  }
}

Each item in start_nodes includes its stable start_node_id, trigger_type, public trigger_config, summary, and available type-specific details. Government-record triggers include the selected target's GovTribe type, ID, and label.

Show the last three runs with the triggers that can start them

{
  "tool": "Search_Automations",
  "arguments": {
    "query": "\"Weekly capture recap\"",
    "fields_to_return": [
      "govtribe_id",
      "name",
      "start_nodes",
      "total_triggers_count",
      "past_runs",
      "total_runs_count"
    ],
    "max_triggers": 10,
    "past_runs_limit": 3
  }
}

Retrieve one known automation by GovTribe ID

{
  "tool": "Search_Automations",
  "arguments": {
    "automation_workflow_ids": [
      "<automation_govtribe_id>"
    ],
    "fields_to_return": [
      "govtribe_id",
      "govtribe_url",
      "name",
      "version_number",
      "start_nodes",
      "total_triggers_count",
      "state"
    ],
    "max_triggers": 50,
    "past_runs_limit": 0
  }
}

When an automation is paused or broken, GovTribe also returns paused_at or broken_details automatically so the agent does not need to request those state-specific fields.

Related articles

• Automation MCP response: Review the response shape returned by this tool.
• Automation data type: Understand the shared record fields and relationships used by this tool.
• Choose a search mode and write queries: Choose keyword or semantic search behavior and shape query values.
• GovTribe AI: Review the GovTribe AI surface where this tool can be called.
• Source identifiers and record matching: Use GovTribe IDs and source identifiers when passing records between tools.