Skip to main content
Glama
734,830 tools. Updated 2026-11-02 08:20

"Tools and Resources for Browser Automation" 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
  • List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.
    ConnectorNo auth
  • List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.
    ConnectorNo auth
  • Change one seller-owned channel's saved listing scope. Read spellbook_inventory_management_get first. Switching legacy all mode to selected mode clears management for all current listings. On an eligible backfilled account, restore_legacy_all explicitly manages every current and future listing on that connected seller account; saved automation settings remain unchanged. In selected mode, use a named candidateId from current SpellBook Finance rows to manage or stop managing a complete listing. Stopping management leaves its live listing and order history intact. These actions save permission for existing automation and do not enable automation or publish a listing.
    Connector
    Destructive
    No auth
  • 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
  • Execute a single external call, and bill on success. Used for any external capability (image/video/audio generation, web search, scraping, email, document parsing, code sandbox, browser automation, embeddings, etc.). The server validates params against a registered schema and proxies to the upstream — you never pass URLs or API keys. Call it directly when you know the exact (service, action, params, max_cost_cents) — from the vaaya skill's catalog or a call you've made before; when unsure, get the call from `consult` rather than guessing.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

  • A real Chromium browser agents can pay for per action over x402 (USDC on Base): navigate $0.005, extract $0.005, accessibility snapshot $0.005, act $0.01, screenshot $0.02, close free. Also runs free self-hosted over stdio via npx @scriptmasterlabs/agent-browser. Six tools with structured error codes and a public receipts log. Source: https://gitlab.com/timothy.walton45/agent-browser

  • Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
    ConnectorNo auth
  • Deletes a SAVED web-automation login profile: closes its window if open, erases its cookies and site data from this Mac, and removes it from web_session_list. Use it to clean up a profile that is no longer needed — web_session_close only closes the window and leaves the login (and its cookies) on disk. IRREVERSIBLE: the next web_login for that name starts from a signed-out browser. Requires confirm=true; without it you get a preview. Verify with web_session_list, which must no longer list the name.
    Connector
    Destructive
    OAuth
  • Get visitors grouped by browser name (Chrome, Safari, Firefox, Edge, and others), ranked by visitors descending, for a date range. Names only: use get_breakdown with dimension browser_version for versions, get_operating_systems for the OS split, and get_devices for desktop versus mobile. Pass filter_browser to other tools to scope them to one browser. Rows carry value, visitors, revenue, and percentage with pagination.total; limit defaults to 100 (max 1000). Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
    ConnectorOAuth
  • Download an English PDF playbook with 7 side-income plays starting under $100. Use when a human wants a full guide. Not for agent automation (use the JSON tools). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $17 Base USDC via x402.
    ConnectorNo auth
  • Download a German PDF guide: 7 legal side-income routes in Switzerland. Use when a Swiss/German-speaking human wants a guide. Not for agent automation (use the JSON tools). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $17 Base USDC via x402.
    ConnectorNo auth
  • When to use standalone media tools (automatic model routing for a single asset) versus workflows (full editable professional video). Call when choosing between generate_* tools and workflow tools. Equivalent to reading the `guidance://tools-vs-workflows` MCP resource — provided as a tool for clients that don't read resources directly.
    ConnectorOAuth
  • Quote one complete enclosure base and lid, with configured hardware, after the customer reviews the exact prepare_enclosure revision. Consumes one quote allowance. Reuse idempotencyKey for retries. Returns a browser link for complete-set checkout; do not use single-part checkout or update tools for these parts.
    ConnectorNo auth
  • Find AI agents, MCP servers and AI developer tools in the AgentIndex directory by keyword and/or category. Use this when the user describes a need ("MCP server for Postgres", "browser automation agent"); use get_trending instead to browse the best tools without a query. Every keyword must appear (case-insensitive) in the name, description, tags or category. Results are ordered by rank_score, highest first. Returns an array of {id, name, category, description, stars, website, github_url, tags, rank_score}; an empty array means no match, so retry with fewer or broader keywords. Pass an id to get_tool_detail for features, use cases and the install command.
    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
  • Change an automation. Its name, description and settings apply at once. definition is the JSON definition {"trigger": ..., "entry": ..., "steps": [...]} and replaces the whole draft, so start from getAutomation, change the JSON and pass all of it back. The whole automation is one JSON document, {"name": ..., "description": ..., "settings": {...}, "definition": {...}}, and name, description, settings and definition here are its parts, with expectedUpdatedAt beside them. The docs page /docs/mcp/tools/automations describes the document, its defaults and its problems. A live automation keeps running its published version until publishAutomation, and contacts already in it stay on the version they entered on. Pass only the parts that change, or the whole document.
    Connector
    Destructive
    OAuth
  • 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
  • Vaaya's deep reference, FREE and instant. Pass `topic` to get the full playbook for a capability area — exact services, actions, params, prices, model lists, and gotchas — the same reference files the vaaya skill ships. Topics: 'setup' (connecting an agent, a chat app, or an unattended process), 'tools' (exact params of every Vaaya tool, GTM suite included), 'media' (image/video/audio models + product-demo videos), 'gtm' (leads, enrichment, outreach, signals, email), 'research' (OneSearch lanes, deep research, company/market research playbooks), 'data' (scraping, people, social platforms, public records, onchain, compliance), 'compute' (sandboxes, browser automation, files, memory, workers, phone calls, llm). Read the matching topic BEFORE non-trivial work in that area — it is cheaper than a wrong call. Never bills; safe to call any time.
    ConnectorNo auth
  • THE approval inbox for V2 rule automation — the ONLY surface for pending automation approvals (MinMax/AOE/scheduled-task tools are separate systems, not this inbox). status=pending (default) means NOT yet approved/dismissed by a user: pending_approval (manual queue + escalations), pending_ai_review (queued for AI Workforce Review — the Automation Review Analyst seat works this queue at its check-ins), shadow (legacy AI Shadow rows; needs your approve/dismiss) and ai_rejected (overridable). Rows carry approval_mode (manual|workforce_review|auto; legacy ai_review/ai_shadow read as workforce_review), rule owner, needs, undoable, and paginate with total_found/truncated/next_offset. scope=mine (default) shows only the calling user's rules; scope=all_users shows every user's. READ-ONLY: action=list. Approving/rejecting/undoing inbox items lives in stage_automation_review.
    ConnectorOAuth
  • Lista os MCP Resources disponíveis com URI, nome e mime-type. Tools de descoberta para clientes que não expõem UI de attachment de resources (como o Claude.ai web). Em Claude Desktop / Cursor / MCP Inspector, resources aparecem em picker dedicado. Resources contêm dados de referência estáticos (tabelas de domínio, glossário, metadados do servidor). Use `compras_obter_resource(uri)` para ler o conteúdo. Retorno: { "total": int, "resources": [ {"uri": str, "nome": str, "descricao": str, "mime_type": str, "tags": [str,...]}, ... ] }
    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