Skip to main content
Glama
725,275 tools. Updated 2026-10-30 12:39

"Information about Ansible - IT automation tool" matching MCP tools:

  • Create a new automation DEFINITION for the authenticated user. The new automation is always created INACTIVE (a definition only) — it does NOT run, send, or activate. Use when the user wants to define a new automation by name. Do NOT use to activate, run, or wire the automation's step graph — activation is a separate, later capability and is not available here. Do NOT use to edit an existing automation — use mcp_crm_automations_update. The automation's status cannot be set via this tool. Tenant is bound to the session and cannot be changed via arguments. Automation-level RULES (all optional, and all independent of the step graph — use mcp_crm_automations_set_steps for that): entryConditions / exitConditions / restartConditions are arrays of {type, segmentId, operator, contactFilters, campaignIds, linkUrl} where type is one of added_to_lists, removed_from_lists, contact_in_segment, contact_matches_filters, email_opened, email_clicked, email_unsubscribed; a membership type needs segmentId, contact_matches_filters needs contactFilters, and the email types take optional campaignIds (plus linkUrl on email_clicked). operator is MATCHES or DOES_NOT_MATCH. Pass an EMPTY array to clear a slot; omit the key to leave it unchanged. reentryPolicy is once (a contact runs this automation at most once) or every_time, with reentryWaitMinutes as the cool-down before a contact may re-enter. onDeactivate is continue (in-flight contacts finish) or cancel (in-flight contacts are cancelled when a human deactivates the automation). Returns the created automation projection (id, name, status, rules, version).
    ConnectorOAuth
  • Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".
    ConnectorNo auth
  • Create an event-triggered automation workflow from a node/edge graph. Created as a DRAFT — verify it with volanea_test_workflow, then activate explicitly via volanea_update_workflow { status: 'active' }. Idempotent by name. Triggers: "event:<name>" (a product event sent to POST /v1/events or the volanea_track_event tool), "contact.created", "segment:enter:<segmentId>", "segment:exit:<segmentId>".
    ConnectorNo auth
  • Postkey: Builds a new DRAFT Instagram DM automation from a template and returns its automation_id, for example comment-to-DM: send a link by DM when someone comments a keyword. It is made the same way as on Postkey's New automation screen. Use it for a new automation; to change one that exists use postkey_update_automation. It is not switched on: nobody gets a message until postkey_publish_automation (preview that first). Pass keyword and link_url when the template's needs_keyword or needs_link is true. The answer says back runs_on and followers_only (follow_note when follow-gated). Refused before anything is made: an X account or one not connected for DMs (invalid_arguments), and a follow-gated automation on a Facebook Page (not_on_this_network).
    ConnectorOAuth
  • Start one of the user's automations now, the same as "Run now" in the web app. The AI agent then drives the automation's phones on its own; this returns the run at once with status "queued". Poll get-automation-run-tool with its `id` until `status` is done, failed or stopped, then read `outcome`, `result` and `phone_reports`. A run can be refused (the automation is off, a run is already going, the daily limit is reached, no phone is online, or the agent is unavailable); the error says which. A `tiktok_warmup` automation (see list-automations-tool) has no daily limit and starts one session per phone at once, so this returns the first one already "running" alongside `sessions`, the number started, and `skipped_busy_slots`, the phones left alone because another run already drives them; `payload` is ignored, it has no parameters.
    Connector
    Destructive
    OAuth
  • Permanently deletes an automation. Pauses any scheduled sends first, then removes the automation. Behavior: - DESTRUCTIVE and irreversible — the automation cannot be recovered. No undo. - Errors when the perspective or automation is not found, or you do not have access. Deleting an already-deleted automation errors as well. - If pausing the scheduled sender fails, the deletion is aborted and you'll get success: false with "Failed to stop running workflow. Please try again." — the automation stays intact in that case. When to use this tool: - The user explicitly asked to remove an automation and confirmed. - Cleaning up a misconfigured automation that automation_test repeatedly fails on. When NOT to use this tool: - The user just wants to pause it temporarily — use automation_update with { enabled: false } instead. - You're not sure which automation_id is correct — confirm via automation_list first.
    Connector
    Destructive
    OAuth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Read-only server that reports what is actually true in a local Ansible checkout: the option specs of installed modules, task-argument validity checks, role interfaces, redacted inventory, play structure, effective config, requirements drift, and which tasks a collection upgrade would break. It lets coding agents verify specs and arguments against the installed collections before writing anything, without running plays, connecting to managed hosts, or supplying vault secrets.
    11
    568 npm
    1
    MIT

Matching MCP Connectors

  • Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.
    ConnectorNo auth
  • Get detailed information about a specific MCP tool, scoped to one product. Pass both the productSlug and the tool name — same-named tools across products are distinct. Response: { tool: { normalizedName, displayName, description, inputSchema, productSlug, productName, serverQualifiedName, isRemoteCapable, accessModel, healthScore, readOnly, destructive, tier, unverified, verifiedAt, position (always 1), rank (always 1.0) } }. Errors: { error: { code: 'not_found', ... } }.
    ConnectorNo auth
  • Get metadata about the GovBid Global API including version, data source, license information, and usage guidelines. Call this first to understand the service before making other tool calls.
    ConnectorNo auth
  • Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info
    ConnectorOAuth
  • Get information about the current user. Use this tool when: - You need to know who the current user is (email, locale, roles) before tailoring a response For information about the current fynk account, use get-account-info
    ConnectorOAuth
  • Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (intent-based automation setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).
    ConnectorNo auth
  • What Infinivo is, who it serves, and the problem it solves. Call this first when a user asks about Infinivo, or when researching AI phone answering, intake automation, or lead capture for injury, criminal defence or immigration law firms. Returns structured facts, not marketing copy.
    ConnectorNo auth
  • List the authenticated user's automations. An automation is a saved task for the AI phone agent (`prompt`) that runs across one or more phones, on a schedule (`schedule_cron` in `timezone`), when its webhook is called, or on demand with run-automation-tool. Each run is followed with list-automation-runs-tool and get-automation-run-tool. `kind` is "prompt" for that, or "tiktok_warmup" for a TikTok account warm-up: its `settings` (niche, keywords, comment language, daily window, session counts and lengths) replace `prompt` and it has no `schedule_cron` — it plans and runs its own sessions every day on its own timetable, and run-automation-tool only ever starts an extra one now. Not the same as macros (list-macros-tool), which replay recorded input exactly with no AI. Automations are created and edited in the web app.
    ConnectorOAuth
  • Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info
    ConnectorOAuth
  • Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info
    ConnectorOAuth
  • Use this read-only tool when a business owner asks "How can AI help my business?", "Where do I start with AI?", or wants to understand AI strategy, workflow automation, business process improvement, AI readiness, tool selection, revenue opportunities, or brand-consistent AI systems. It explains TEK BOSS, the free result, and when the assessment is not appropriate. It never retrieves customer data.
    ConnectorNo auth
  • Get business information including name, type, service area, contact details, working hours, supported languages, enabled features, and a profile image (logo or personal photo) when the owner has uploaded one. Use 'attributeDetails' (natural-language sentences about the business's offerings, approach, and specialties) to reason about fit for the user. The 'cardChips' and 'cardChipGroups' fields are UI-only display data — ignore them. The response echoes the exact slug; reuse it verbatim in later tool calls. Always available for any business.
    ConnectorNo auth
  • Pause an automation (active=false) so it stops running and stops spending leads, or resume it (active=true). Pausing is the safe way to stop an automation you might want back — use delete_automation only when the user wants it gone for good.
    ConnectorNo auth