Skip to main content
Glama
309,543 tools. Last updated 2026-07-28 07:18

"A tool or method for viewing the unrendered HTML/JavaScript of a webpage" matching MCP tools:

  • Submit an uploaded PDF for faxing. Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.: curl -F "file=@document.pdf" https://www.sendthisfax.com/api/upload fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile}) The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages. Step 2: call this tool with the fax_public_id and the recipient fax number. Two modes: - With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits. - Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid. In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded). For integration testing, +19898989898 is the designated test recipient number.
    Connector
  • Generate a PDF or Excel document from HTML (document_content) or a URL (document_url). Exactly one of document_content / document_url is required. By default the document is HOSTED and the tool returns a { download_url } you can fetch — ideal for agents (no large binary in the response). Set hosted:false to get the raw document back as base64, or async:true to enqueue a job and poll docraptor_get_document_status. IMPORTANT: real documents consume account credits (billed). Set test:true to generate a FREE, watermarked document while developing. DocRaptor API: POST /docs.
    Connector
  • Fetch the fully rendered HTML of any web page through the ScrapeUnblocker API (https://developers.scrapeunblocker.com), bypassing anti-bot protection (Cloudflare, DataDome, PerimeterX, Akamai, Shape). Use when a normal fetch is blocked (403/429, captcha) or the page needs a real browser. Returns raw HTML.
    Connector
  • Log a note against a contact or a listing in YOUR agency's CRM (e.g. record a call outcome or a viewing). Provide the note text plus a contact_id (from find_contacts) and/or a property reference. The note appears on the contact/property timeline. Requires an agency API key.
    Connector
  • Starts a data-driven prompt optimization job on Vertex AI. This method uses a dataset and configurable metrics. The `config_gcs_path` must point to a JSON file in Google Cloud Storage. Args: config_gcs_path: The Google Cloud Storage URI (e.g., "gs://your-bucket/config.json") to a JSON file containing the Prompt Optimizer configuration. This is required. service_account: The service account email to run the job. This is required. prompt_optimizer_method: The method for prompt optimization. Either 'VAPO' or 'OPTIMIZATION_TARGET_GEMINI_NANO'. wait_for_completion: If True, the tool will block until the Vertex AI CustomJob completes. Defaults to False. Returns: A string indicating the status and details of the optimization job, including a link to the Vertex AI console.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Create sandboxed public-unlisted or access-key-protected HTML previews through a remote MCP server.

  • Manage your Canvas coursework with quick access to courses, assignments, and grades. Track upcomin…

  • Applies few shot prompt optimization to a prompt using user provided dataset and method. Args: prompt_to_optimize: The zero-based index of the prompt to improve. example_path: GCS path to the csv file containg few-shot examples method: The optimization method to use for few shot prompt improvement. The method should be one of the following: - TARGET_RESPONSE: Optimize the prompt to match the target response. - RUBRICS: Optimize the prompt to improve the rubrics scores. Returns: Optimized prompt.
    Connector
  • Render a web page (by url) or raw html into a pdf and return it as base64 pdf data. Provide exactly one of url or html. Respects robots.txt for url input. Pass api_key if you have a pagewatch key, otherwise a free trial key is created for you and returned. url: the page to convert, optional. html: raw html to convert, optional (provide url or html, not both). api_key: an existing pagewatch bearer token, optional. paper: A4, Letter, Legal or A3. landscape: landscape orientation.
    Connector
  • Fetches any public web page and returns clean, readable plain text stripped of HTML, navigation, scripts, advertisements, and boilerplate. Returns the page title, meta description, word count, and main body text ready for analysis or summarisation. Use this tool when an agent needs to read the content of a specific web page or article URL — for example to summarise an article, extract facts from a page, verify a claim by reading the source, or convert a web page into plain text to pass to another tool. Pass article URLs returned by web_news_headlines to this tool to read full article content. Do not use this tool to discover current news headlines — use web_news_headlines instead. Does not execute JavaScript — best suited for standard HTML content pages. Will not work with paywalled, login-protected, or JavaScript-rendered single-page applications.
    Connector
  • Fetch a URL with full reliability — retry, circuit breaker, cache, and anti-bot bypass. Returns both raw HTML and clean markdown. Automatically retries on failure with exponential backoff, falls back to plain HTTP if browser fetch fails, and circuit-breaks domains that are consistently down. Args: url: The URL to fetch use_cache: Whether to use cached results (default: true, TTL 1 hour) js_render: Whether to render JavaScript (default: true, disable for speed) wait_for: CSS selector to wait for before capturing (e.g., '.results-loaded')
    Connector
  • Host a self-contained HTML page at a stable, default-private, shareable URL — the Artifact experience, in-app. Pass **exactly one** of: - `html` — the full page: your `<body>` plus any `<style>`/`<script>`. Unlike documents.create, the page is served **live** (JavaScript runs), so charts, interactivity, and small tools work. - `file_id` — a workspace file whose contents are already the HTML page. - `analytics_card_ids` — ids of saved analytics dashboard cards; the platform re-runs their queries and composes one designed report page (static charts, snapshot at build time). Best way to give someone a shareable analytics report. The page runs in a locked-down sandbox: a dedicated origin + a strict CSP. That means it is **fully self-contained** — it CANNOT call out to the network (`fetch`/XHR/WebSocket are blocked) or load anything from a CDN. Inline all assets: CSS/JS inline, images/fonts as `data:` URIs. Draw charts yourself as inline SVG (no external chart library). `access_level` defaults to `'private'` (viewable only in-app). Set `'shared'` to make the unguessable link itself the capability (anyone-with-link). You can flip this later with artifacts.set_access. Returns `{artifact_id, slug, url, version}`. `url` is the live link when the public origin is configured; until then the artifact is hosted and versioned but `url` is null. Republish with artifacts.update — the URL stays the same.
    Connector
  • Re-render a data-driven artifact from a small data payload and publish a new version at the SAME URL. The artifact must have been created/updated with a `template` (HTML containing {{placeholder}} tokens). Pass `data` as a flat map of placeholder -> value (e.g. {"leads": "3 200", "date": "15 июля 2026"}); the server substitutes them into the stored template — you do NOT send any HTML. Ideal for scheduled refreshes of live numbers. Every template placeholder must have a value in data, or the call fails.
    Connector
  • Get the embed code snippet for a livechat widget. Returns HTML/JavaScript code to add to your website. The code should be placed before the closing </body> tag. Use this when user wants to install the chat widget on their site.
    Connector
  • Get detailed information about a specific LOINC code. Use this tool to: - Get the full name and description of a LOINC code - Find the component, property, timing, and system - Check the scale type and method Provide a LOINC number in format "XXXXX-X" (e.g., "2339-0" for Glucose).
    Connector
  • Core dossier check: Send a CORS preflight OPTIONS request to https://<domain>/ and return the access-control-* response headers. Use to verify CORS policy for a specific origin-method pair, or to check whether a domain allows cross-origin requests; provide origin and method to simulate a precise preflight, or omit to use defaults (origin: https://domainposture.com, method: GET). Single OPTIONS request via fetch, 5 s timeout. Returns a CheckResult: on success, {status:"ok", headers:{access-control-allow-origin,...}}; on failure, {status:"error", reason}.
    Connector
  • Identify the technology stack and services used by a website. Returns framework names, CMS platform, JavaScript libraries, analytics services, CDN provider, hosting provider, and security tools detected. Use for competitive analysis, vendor intelligence, or understanding site architecture.
    Connector