"How to Retrieve Console Logs" matching MCP tools:

• get-logsA

  mcpA

  Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).

  ConnectorNo auth

• get_setup_instructionsA

  Vilix AIA

  Make Vilix automatic. Call this when the user asks "how do I make this automatic", "set this up so it remembers on its own", or right after a first connection when offering setup. Returns a short custom-instructions block the user pastes into THIS tool's personalization / custom-instructions settings so the AI starts calling Vilix (get_context / save_turn) on its own — plus exactly where to paste it. `recommended` is the block matched to the caller's tool; `blocks` lists every supported tool's block (and for headless always-on tools, an enforce-every-turn variant for an always-on rules file). `source` (optional) — the tool label you run in (e.g. "ChatGPT", "Claude", "Cursor", "Codex", "Copilot", "Windsurf"), used to pick the right block; omit to get the generic default. This is an OPT-IN setup you hand to the user — it is not auto-applied; Vilix logs nothing silently.

  ConnectorOAuth

• get_wedding_informationA

  The Hill KinabaluA

  Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.

  ConnectorNo auth

• portal_evm_query_logsA

  SQDA

  Query raw EVM logs with address/topic filters, common event aliases, earliest/latest scanning, and optional inline decoding. COMMON USER ASKS: - Recent USDC Transfer logs - First recent USDC Transfer log - Latest ERC721/pass mint ID and tx hash FIRST CHOICE FOR: - NFT or ERC721 mint lookups such as latest pass minted, token ID, and mint transaction hash - contract event questions where the user needs exact event evidence rather than wallet or transaction summaries WHEN TO USE: - You need event logs filtered by contract or topic signature. - You want decoded log hints while still keeping the raw log shape available. - You want the first or last matching event in a bounded block/time window. - You want common event names such as transfer, approval, swap, mint, or burn instead of remembering topic0 hashes. - You need the latest ERC721/pass mint in a bounded deployment/recent window: filter Transfer events with topic1 as the zero address, use scan_order=latest, limit=1, and decode=true to expose decoded_log.decoded.token_id plus transaction_hash. DON'T USE: - You only want token transfers, which are easier with the token-transfer tool. EXAMPLES: - Recent USDC Transfer logs: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","limit":20} - First recent USDC Transfer log: {"network":"base-mainnet","timeframe":"1h","token_symbols":["USDC"],"event":"transfer","scan_order":"earliest","limit":1} - Latest ERC721/pass mint ID and tx hash: {"network":"base-mainnet","from_block":46020000,"to_block":46100000,"addresses":["0xE4E70FdF2Fc1147a7f35c4c5de88E6BeA63eeAfA"],"event":"transfer","topic1":["0x0000000000000000000000000000000000000000000000000000000000000000"],"scan_order":"latest","decode":true,"include_transaction":true,"limit":1} - Decode logs inline: {"network":"ethereum-mainnet","timeframe":"1h","topic0":["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"],"decode":true,"limit":10}

  ConnectorNo auth

• lemma_get_schemaA

  mcpA

  Retrieve a Lemma schema by its ID via GET /v1/schemas/{id}. A schema declares how documents of a given type are interpreted and normalized. Returns SchemaMeta { id, description? } with additionalProperties open — implementations commonly include a `normalize` artifact (WASM that maps raw documents to canonical form) and its content hash. Use this when you need to interpret attribute keys returned by lemma_query_verified_attributes.

  ConnectorNo auth

• deploy_logsA

  LayeroA

  Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the cause is vague, or you are interested in how the app behaves rather than in a failure. You get the TAIL. `truncated` says earlier lines were dropped; do not present the tail as the whole log. For build logs, package-manager network chatter is hidden BEFORE the tail is cut, so the tail holds meaningful lines; `noise_hidden` says how many were hidden and `include_noise=true` shows them.

  ConnectorOAuth

• deploy_logsA

  LayeroA

  Raw log lines — for when the `diagnose_deploy` analysis was not enough. Start with `diagnose_deploy`: it has already pulled out the cause and the neighbourhood of the fatal line. Come here when you need to look with your own eyes — the cause is vague, or you are interested in how the app behaves rather than in a failure. You get the TAIL. `truncated` says earlier lines were dropped; do not present the tail as the whole log. For build logs, package-manager network chatter is hidden BEFORE the tail is cut, so the tail holds meaningful lines; `noise_hidden` says how many were hidden and `include_noise=true` shows them.

  ConnectorAPI key

• get_logA

  FixterA

  Fetch a single log by its logId: all attributes flattened in (plus a `resource` object) and the message. Use after a lean `logs` scan when you need the body of one row. A value longer than 4000 characters is cut and shows a marker; read the rest with path. For custom column selection use run_sql. Reading one long value: pass path to get one value of the log, in full or in slices. A run_sql, logs or get_log result that cut a long value shows a marker with "truncated": true, the value's full length (chars), its structure (keys) and a "more" call that reads on. Parameters for a slice: logId; path, what to read: message, an attribute name (exception.stacktrace), or a JSON path into a value holding JSON (body.items[2].name); find, text to jump to: the slice starts just before its first match at or after offset; offset, the character position to start at (default 0); length, how many characters to return (default 20000, max 50000). A slice returns: logId, path, chars (the value's full length), offset, text (the slice), nextOffset (null once the slice reaches the end), matches (every place find matches in the whole value, up to 20, each with its offset and the text around it; the slice starts at the first one at or after offset), and keys (the structure of the value at path, when it is JSON). To read on, call again with offset=nextOffset; to read another match, call again with offset set to that match's offset. Returns (no path): the log object.

  ConnectorAPI key

• storage_publishA

  TeamSharedC

  Publish a Storage object and return a presigned bucket GET URL. Idempotent: returns the existing token if already published. Does not re-upload bytes (they already live in the bucket). Agents should use ``signed_url`` (TTL ``TEAMSHARED_STORAGE_SIGNED_URL_TTL_SECONDS``, default 3600s) plus ``signed_url_expires_in`` / ``signed_url_expires_at``. ``share_url`` / ``public_url`` remain the durable ``/d/{share_token}`` fallback for console/humans — not ``/s/{slug}`` (shared-file HTML). Fails closed if the object-storage bucket is unconfigured (cannot mint a signed URL). Agent seats (org ``tsk_`` / ``agent_run``) are refused — call ``request_gated_approval(gate="publish")`` instead. Console humans (``ts_session``) still publish. After the approval child is done, a human seat calls this tool (same completion path as ``file_publish``).

  ConnectorNo auth

• get_page_performanceA

  SEO GSC Wizard MCPA

  Use this when the user asks how one specific page performed day by day. Daily performance for a single page (clicks, impressions, CTR, position). Useful for diagnosing post-deploy regressions on a specific URL. Not for a ranking of pages: use query_top_pages. `pageUrl` must match the URL exactly. Rows run by date, oldest first; days without impressions are absent, not zero. `ctr` is a 0-100 percentage. Served from the ClickHouse warehouse when available, otherwise the live Search Console API (see `dataSource`). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

  ConnectorOAuth

• get_cross_site_summaryA

  SEO GSC Wizard MCPA

  Use this when the user asks how all their properties are doing, or which gained or lost most. Aggregates a last-N-days clicks/impressions summary across the account's registered Search Console properties (optionally filtered to those carrying a given tag), with a same-length prior period for comparison and per-site totals. Without a tag it also covers properties shared with the account (marked `shared: true`; tags are the caller's own, so a tag filter covers owned properties only). The MCP equivalent of the app's Global Reports page. Set `includeSearchTypes` to also split every property across web / image / video / news / discover, and `includeCountries` for a country leaderboard aggregated over the whole portfolio; their ctr and clickShare are 0-100. perSite and countries are sorted by clicks, descending. Each site routes independently to the ClickHouse warehouse or the live Search Console API, so `dataSource` is reported per site; a site whose read fails, or a share that no longer grants access, is reported in `errors` with a `reason` rather than failing the whole call, and the totals then cover only `sitesIncluded` properties, which `warning` says. Not for one property: use get_site_summary; for a tag's daily trend and top queries and pages use get_tag_group_view. Processes at most `maxSites` properties per call (default and maximum 100; `scope.truncated` says when more matched, so narrow by `tag`). The rate-limit cost scales with the number of properties and the breakdowns requested.

  ConnectorOAuth

• get_ga4_overviewA

  SEO GSC Wizard MCPA

  Use this when the user asks how much GA4 traffic a site had, or how it changed against the previous period. GA4 summary for the property linked to a GSC Wizard site: sessions, active/total/new users, page views, engagement rate, session duration, bounce rate, event count, and key events, with an automatic previous-period comparison (`prevSummary`). Not for Search Console clicks: use get_site_summary; for a split by channel or page use query_ga4_report. When the comparison period has no GA4 data at all (e.g. before the data stream existed), `comparisonHasData` is false and prevSummary is null instead of all zeros. Set `includeTimeseries` for daily points (`timeseries`, oldest day first). engagementRate and bounceRate are fractions 0-1, not percentages; averageSessionDuration is in seconds. Returns `notConfigured` (with a reason and hint) instead of data when Google Analytics is not connected or no GA4 property is linked to the site in GSC Wizard. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

  ConnectorOAuth

• get_merchant_listings_performanceA

  SEO GSC Wizard MCPA

  Use this when the user asks how visible their product results are in Google web Search, and which product pages carry them. Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline in date order, and the top pages (product URLs) behind it; appearances and pages are sorted by clicks, highest first, and CTR is a 0-100 percentage. Search Console merchant listings counts enriched product results in web Search only, so it does not reconcile to one figure with Merchant Center free listings. Not for the Shopping tab, Images, Lens, YouTube or Maps: use get_organic_shopping_performance. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, and `emptyBecause` is set whenever it has no impressions, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

  ConnectorOAuth

• data_writeA

  Tunc OrbA

  Save new data to the user's Tunc Orb: create a named record, or append entries to a log (it is created when absent). Use it when the user asks you to save, record or hand off something, such as a note, decision, approval, result, processed-item state or resume point. Records and logs are kept until deleted. Give each record a clear name and a one-line about so it can be found again, and look the name up with data_read first so you do not create an overlapping record. create never overwrites an existing record and append only adds entries, so no record or log entry is changed or removed: change a record with data_update and remove data with data_delete. When storage is full, saving removes the user's oldest saved files first to make room and the result says how many were removed; records and logs are never removed to make room. Batch log entries. Each call sends at most 64 KiB (one value, or one batch of log entries); a record can hold up to 16 MiB, so grow a larger one with data_update patches. When a record points at a stored file, keep the file's artifact_id, not its viewer link: the id opens the file with art_read, and the link is only for people. The service handles encryption and storage; when you retry a call, send the same mutation_id so it never applies twice.

  ConnectorAPI key

• storage_archiveA

  TeamSharedC

  Soft-archive a Storage file or an empty Storage folder. Same as console **Archive** on ``/app/storage``: the row's status flips to ``archived``, lists and attachments hide it, bucket bytes and join rows stay. Folders must be empty — a folder with active children is refused with ``folder_not_empty`` (move or archive its children first; archive never cascades). Returns ``{file_id, archived: true}``, or ``archived: false`` with ``reason="not_found"`` for an unknown or already-archived id. Needs ``memory:delete``, as console archive does. Not a purge: there is no hard delete of Storage objects. Shared-file documents use ``file_archive``.

  ConnectorNo auth

• list_dataset_idsA

  Google Big QueryA

  List BigQuery dataset IDs and BigLake namespaces in a Google Cloud project. Supports pagination. Use `page_size` to limit results and `page_token` to retrieve next page.

  ConnectorNo auth

• marketing_get_reportA

  Google Analytics (unofficial)A

  Primary reporting tool for a given GA4 property or site. Use for totals, trends, and breakdowns by dimension across GA4 website traffic and app analytics, Google Search Console site traffic, and Bing Webmaster — including last-30-days summaries, revenue, leads, sessions, users, engagement/time-on-page (average_session_duration, user_engagement_duration), and period-over-period comparisons. Drill deep: GA4 supports up to 9 grouped dimensions (date/hour, geo, device/browser/OS, source/medium/channel, landing_page/page_path, etc.). Defaults to all mapped connected sources merged into one standardized view, aligned on the shared grain (typically landing_page) so a page row blends GA4 sessions+engagement with Search Console/Bing clicks/impressions/CTR/position; per-source detail (e.g. full query lists) stays in sourceSections. Note GA4 has no `query` dimension and Search Console/Bing have no sessions/engagement, so those cannot share one row — query is a Search Console/Bing breakdown. Narrow with sources or sourceMode='single'. Any GA4 dimension/metric name not in the catalog is passed through to the GA4 API automatically; metricMode='source_native' forces a pure GA4-native report. Pass one date range for a single window or two date ranges for period-over-period comparison.

  ConnectorNo auth

• how-toA

  Fast.ioA

  Built-in product help — a natural-language "how do I…" question about Fastio returns a grounded, product-aware answer (or a short clarifying question) in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything); the actions themselves are on the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls, in place of guessed endpoints or exploratory calls. Q&A over the user's uploaded files (RAG) is the `ai_manage` tool; `how-to` answers questions about Fastio ITSELF. Costs no credits; needs only an authenticated user (no org needed). action='describe' gives the full action/param reference.

  ConnectorNo auth

• debugA

  1inch MCPA

  [Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Look up production API request logs for your 1inch Business organization to troubleshoot integration issues. Results are always scoped to your authenticated organization. Two modes: 1) By request id: pass requestId (the x-request-id header returned on 1inch API responses). Optionally narrow startTime/endTime (defaults: last 24 hours ending now). 2) Logs in a time window: omit requestId and pass both startTime and endTime (RFC3339). Optionally set logLevel ("info", "warn", or "error") to filter by severity; omit to return all levels. Limits: each call covers at most a 24-hour window; how far back you can query depends on your plan's log retention.

  ConnectorNo auth

• create_shareA

  agent4.ioA

  Create a **share / integration entry point** for an agent — this is how end users actually reach it. **`published=True` only means "visible", not "reachable"**: for end users to talk to the agent you must create a share. The response carries a directly openable chat link (`{public_base}/s/<token>`) and the website embed URL (`{public_base}/embed/<token>`). For a website widget, paste one line before </body>: `<script src="{public_base}/embed.js" data-token="<token>"></script>`. label names this entry point ("website widget", "support link"). Telegram/WhatsApp and other channels are connected separately on the agent's Integration page in the console. **No website?** Hand the returned `chat_url` or `qr_url` (QR code) straight to the tenant: print it on business cards / flyers / in-store; scanning opens a full-page chat, no login, returning visitors are remembered per browser. **For links you give to humans, prefer `pretty_url`** (when present in the response): `{public_base}/t/<tenant alias>/<agent alias>` — memorable, printable, survives token rotation. No pretty_url = aliases not fully set — **fix that proactively**: agent alias via `create_agent`'s alias param or `PUT /agents/{name}/alias`; tenant alias in console → Settings. The `/s/<token>` link still works, but it is the machine/embed form, not one to read out to a person.

  ConnectorNo auth

• logsA

  FixterA

  Find logs matching filter criteria within a time range. Use this as your default starting point for log queries. Returns logs sorted by (timestamp, logId) descending (newest first). When investigating an error or a failure, call list_issues first: Fixter has often grouped it already into an issue with its count, first and last seen and a traceId to search from. Returns the log's main fields by default; pass verbose=true to include its attributes (http/url/… flattened in, plus a `resource` object). Long string values are capped (maxStringChars). For raw columns or custom selection use run_sql. For one row with every attribute, use get_log; a cut value's marker carries the "more" call that reads the rest. Defaults: from: 1 hour before to (or before now) when omitted; set it to read further back to: now when omitted limit: 100 (max 1000) service/level: any Common patterns: - Errors in the last hour: level="ERROR", from=<1h ago> - Logs for a trace: traceId="abc123..." - Whole-token search (case-insensitive): messageContains="timeout" - Substring or regex search: not supported here; use run_sql Returns: logs: array of log objects (lean unless verbose=true) nextCursor: opaque token (null on the last page); pass back as cursor to fetch the next page truncationHint: present when the page was cut to fit the response; nextCursor then reads on from the last log shown explorerUrl: shareable Fixter UI link opening this query in the log explorer — when the user asks to see or browse these logs, send them there rather than reproducing the listing; attach it when citing these logs as evidence (covers the service/level/traceId filters and the window; timestamps display in the viewer's browser timezone) queryStats: rowsReturned, elapsedMs

  ConnectorAPI key