Skip to main content
Glama
806,900 tools. Updated 2026-11-19 14:22

"Creating PowerPoint presentations in custom design" matching MCP tools:

  • List all slide presentations (slides, powerpoint, deck, keynote). Use this when asked to list, find, or search presentations, decks, or slideshows.
    ConnectorNo auth
  • List all slide presentations (slides, powerpoint, deck, keynote). Use this when asked to list, find, or search presentations, decks, or slideshows.
    ConnectorNo auth
  • Replace a form's custom variables — named values that logic rules read and write (scores, prices, outcome tallies). Pass the COMPLETE custom list from list-logic-options-tool, excluding entries with built_in true. Names use letters, numbers and underscores only; type is "number" (starts at 0) or "text" (starts empty). Built-in and field names are reserved. Create every variable BEFORE referencing it in set-block-logic-tool. Changes apply to the live form immediately. To remove or change the type of a variable in use, remove its references from the draft and publish first.
    Connector
    Destructive
    OAuth
  • Get the caller's own role and effective permission strings in the active organization — custom roles resolved. This is the tool to reach for after a permission error: it says what the caller actually holds. Set includeCatalog to also get every permission the product defines with its description, to map a denied action onto a name. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Applies the buyer's field values (and logo, if the template needs one) to a template, fits the text to its printable area, renders both sides as preview images, and returns a design token. Before creating a guest design, explain: unpaid, unsaved drafts expire 30 days after the design request starts. Verified saving keeps the draft; checkout and unresolved purchase artwork is protected. Seven-day token expiry is separate from deletion. Call list_business_card_templates first and collect a non-blank value for every field it lists, keyed by `attribute`; a blank or missing value fails with missing_required_fields. Pass a public https PNG or JPEG URL as `logoUrl` only when the template has an imageUrl field; omit it otherwise. Returns designToken, designId, templateId, revisionId, expiresAt (7 days out), previews (a 300-second signed URL plus width/height for each side; the pixels are also attached as image content blocks), and any text_shrunk warnings from fitting a value to its layer. Present both attached proof images directly, or provide labeled front/back links to the exact preview URLs if the host cannot display them. Do not require computer setup, downloads or re-uploading for proof review. Refresh expired links rather than creating another design. An accountOwned result identifies a verified customer, not an integration key. Results also include a private saveUrl for browser ownership verification; offer it only when the buyer wants to save. Saving requires sign-in; subsequent checkout of that design requires an AI connection authorized by the same InkFE account. If customer OAuth is unavailable, complete checkout before saving. Use a stable requestId; retry the same request after a timeout. Revise with revise_business_card_design and refresh expired links with refresh_design_proof. Show both previews and warnings, get exact print options and get_quote, then record explicit customer approval with approve_design_proof before create_checkout. Fails with unknown_template, missing_required_fields {attributes}, unknown_field {attribute}, value_too_long {attribute}, unsupported_characters {attribute}, logo_required, logo_fetch_failed, logo_unsupported, rate_limited {retryAfterSeconds} (too many designs from this API key in a short time), or connector_unavailable.
    ConnectorNo auth
  • Only for anonymous callers when guest access is enabled. If this AI app is already connected through InkFE customer sign-in (OAuth) or a provisioned integration key, skip this tool and omit guestToken on design/checkout calls. Before guest designing, tell the customer: unpaid, unsaved guest drafts expire 30 days after the design request starts; save through verified sign-in to keep them. Checkout or unresolved purchase records are protected. Returns a private guestToken valid for seven days; token expiry is separate from draft retention. Pass it to create_business_card_design and create_checkout in this conversation. Claimed designs require an AI connection authorized by the same InkFE account. Starting a session does not place or pay for an order.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Create narrated presentations from HTML, poll build status, list them, read one back as text.

  • Generate, edit, merge, translate and PDF-convert PowerPoint (.pptx) over MCP. 8 tools.

  • Planning-time statistical power from a design's REAL model matrix — no data needed. Builds the design and takes `ncp = effect_size² / (X'X)⁻¹_jj`, so it is correct for centre points, axial points and unbalanced designs — unlike `covadoe_power_analysis`, which assumes orthogonality and overstates power on a CCD, Box-Behnken or DSD. Use this when planning an experiment; use `covadoe_post_hoc_power` only once you have measured responses. `design_type` + `n_factors` builds the design (same generator as `covadoe_create_design`, so the answer describes the design you would actually get). Common aliases resolve ("full_factorial", "ccd", "dsd"). Alternatively pass `design`, an explicit coded run matrix, to score a design you already hold — D/I-optimal, mixture, split-plot or hand-built. `n_runs` / `model_terms` are forwarded to the generator for the optimal designs. `model`: "linear" | "interaction" | "quadratic" | "quadratic_no_interaction" (a DSD supports only the last). `term` names the coefficient — "x1", "x1^2", "x1*x2"; omit it to get power for every term and group, which differ sharply on the same design. `alpha` is the significance level; the CCD axial distance is `axial_alpha`, and the two are easy to confuse. CCD variant: `axial_alpha` defaults to ROTATABLE, (2**n_factors)**0.25 — the design JMP, Design-Expert and Minitab hand you. Pass a number, or "orthogonal" for the α where Σx² = n_runs (at 3 factors: main-effect power 0.9400 against the rotatable 0.8846 on the same 17 runs; the orthogonal α is also the premise of `covadoe_power_analysis`, so on that design the two agree for a main effect and disagree for every other term). `face` — "circumscribed" (default), "faced" (star points on the faces, α = 1) or "inscribed"; a bool works, and an unknown value is rejected rather than quietly treated as circumscribed. Returns power, power_by_term, power_by_group, df_error, relative_variance ((X'X)⁻¹_jj), the resolved design_summary (the α and factorial level actually built — read both, an inscribed CCD always reports α = 1), and `orthogonal_shortcut_power` — what `covadoe_power_analysis` would have claimed — with its signed error (signed: the shortcut does not always overstate). Returns `estimable: false` plus a reason when the model cannot be fitted on the design.
    ConnectorAPI key
  • Define a new custom smart field, a merge field signature templates and campaign conditions can use. Check list_smart_fields first: labels are unique, and to rename, retype or rebind an existing field use update_smart_field instead. A manual field starts empty; set each teammate's value with update_teammate. Bound to an integration (integration_id + integration_attribute), its values come from that integration and update_teammate can no longer set them; integrations do not fill url fields, so keep a url field manual. Creating the field changes no signature until a template references it. Writes one field and returns it. Needs the smart_fields:write scope; a taken label, an invalid kind or an unknown or unsuitable integration returns 422.
    ConnectorOAuth
  • Create a new, empty signature folder to organize signature templates. Folders created here are top-level (not nested). Use it only when no suitable folder exists: call list_folders first to reuse one, and use update_folder to rename an existing folder instead of creating another, since duplicate names are allowed. Creating a folder files nothing: to put a signature in it, pass the returned `id` as `folder_id` to create_signature or update_signature. Writes one folder and returns it with `signature_count` 0. Needs the folders:write scope; a blank name returns 422.
    ConnectorOAuth
  • Publish a site to make it live on the web at its platform address (the `deployment_url` in the response is the exact live URL — report that, never guess a host). Choose a subdomain matching the business name (lowercase, hyphens). IF THE SITE STILL HOLDS SEVERAL DESIGNS you MUST pass `variation_id` — the design to publish, taken from list_variations (a UUID, not an index). Do not choose for the user: list_variations attaches a thumbnail of each design, so show them and let the user pick. Publishing a design turns it into its own site: Mondovo builds the chosen design into a new site and publishes THAT, so the response carries a different `site_id` — use that id from then on (the original id stays the design draft, and get_site on it will keep saying unpublished). Calling publish twice reuses the same built site rather than creating another. Sites that already have one design ignore `variation_id`. A design only has its home page, but its menu links to the rest of the site: when it does, publish_site first BUILDS those pages and then publishes automatically — it returns status "building" with `pages_being_built`, a `job_id` and the new `site_id`. Before publishing a design, tell the user which pages its menu links to and that they will be built. On "building", tell the user which pages are being built, poll get_job with the job_id until "completed" (`failed` lists pages that could not be built — their menu links are removed; `publish` says whether the site went live), then poll get_site until "published". Do not call publish_site again meanwhile. If a response carries `missing_pages`, those menu links have no page and 404 on the live site: tell the user and offer add_pages for them. This tool RETURNS IMMEDIATELY with status "publishing" once the site is accepted for deployment — it does NOT wait for the deploy. Compiling and deploying takes 1-3 minutes and continues server-side even if this conversation ends. Poll get_site (with the returned site_id) every ~15s until status is "published" to get the live URL — or "publish_held", which means the new build crashed in a browser check before going live and was not published (tell the user its `publish_message`). NEVER call publish_site a second time to check on or hurry along a publish you already started: while one is in flight the publish lock rejects the call, and a transport timeout on this tool does NOT mean the publish failed — it is almost always still running, so poll get_site before concluding anything. If the response is `contact_info_needs_confirmation`, its `reason` says why: "placeholders" means contact details that look AI-invented (listed in `placeholders`) — refine them to the real values first, or (if they are already correct) call again with `confirm_contact_info: true`; "missing_details" means nothing was invented but the email or phone in `missing_fields` is absent — ask the user for it, or call again with `confirm_contact_info: true` if the site should go live without it. Never make up a contact detail. Retrying with the same arguments will NOT clear that warning. Success responses carry `after_publish` (plan, custom domain, editor link): once get_site reports "published", relay its `tell_user` to the user.
    ConnectorOAuth
  • Changes this project's name, website, environments, email prefix or default mail domain, as in Project settings, and which fields with no custom field get a guess (fill_unknown_fields). Only the fields given change. The name, website, environments, prefix and domain need the project's lead (or an organisation owner or admin), the same as in the app; fill_unknown_fields follows the custom fields' rules: anyone on the project, unless only its leads change custom fields. Every change is in the project's activity log. Archiving or deleting a project, and keeping whole emails, stay in the app. Returns the project as get_project does.
    Connector
    Destructive
    OAuth
  • Use this to put a Pin back to the original photo the design was built from, discarding the generated design. Free and instant. Only works when get_pin_design lists "revert" in supportedOperations, which requires the Pin to still carry its original photo. The generated variations remain available, so this is reversible with select_pin_design_variation. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.
    ConnectorOAuth
  • Delete layers from a design, with everything inside them and their motion. Returns the deleted layer ids (and any `skipped` with skip_missing). If one id is not on the design the call is refused and nothing is deleted. Saved as a new revision: undo brings the layers back, but only until the next change is undone past. Use it to remove layers the design no longer needs; to hide one for now set visible: false with update_layers, and to remove a whole page use delete_page.
    Connector
    Destructive
    OAuth
  • 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
  • Create a new list for the user (e.g. 'make a Costco list', 'start a party list', 'set up a baby registry'). Defaults to a shopping list. The list appears in the user's LastList app and is labeled as created by you. Ask the user before creating a list they didn't request.
    ConnectorOAuth
  • Read remaining quotas and plan entitlement for the authenticated company. Call this when you need to know whether an active plan is in effect before registering OIDC clients or creating login links. Creating login links, minting extra API keys, and registering end users all require an active plan (the bootstrap key does not). Requires a company API key (aa_...) or an MCP OAuth access token. Returns planId, planStatus, periodYm, included, used, remaining, and hardCap. It does not change billing or charge a card. To start a human Pro checkout, use billing_checkout. billing_machine_pay only returns prepaid REST instructions. To manage an existing Stripe subscription, use billing_portal.
    ConnectorAPI key
  • Claims `hostname` for this website and registers it with the Cactal edge. Custom domains must first be enabled for the website (`websiteDomains.setEnabled`, owner-only — enabling is the billing moment); the request fails with 403 `custom_domains_disabled` otherwise. Adding or removing domains on an enabled website never changes billing. The domain is created in `pending_dns` status, and the returned `dnsRecords` list exactly what to create at your DNS provider: an ownership TXT record on `_cactal.<hostname>` plus a routing record (a CNAME for subdomains or an A record for apex domains). Hostnames must be lowercase ASCII domains (not IP addresses or Cactal platform hosts), each website can have at most 10 custom domains, and a hostname can be claimed by only one website; claims that never verify expire after 7 days. After creating the records, call the verify endpoint or wait for the automatic re-checks.
    ConnectorOAuth
  • Start a PowerPoint presentation built by Claude (POST /api/v1/presentations). Paid by actual usage. The balance is charged when the agent finishes each turn; a turn that ends with no result is refunded. With too little money on the balance the answer is 402 INSUFFICIENT_BALANCE and nothing is started. This is a long task of several minutes: the answer comes at once with an id and status running. Do not wait for it in this call; fetch the result with get_presentation until status is awaiting_input (a turn is done) or failed. Needs brief (the topic, audience, goal and facts to use). tier is fast by default (Claude Sonnet 5.5 with an Opus 5.5 advisor) or pro (Claude Opus 5.5 for the whole deck, costs more): use pro only when the user asks for the best quality or the chat model is Claude Opus. Optional title and file_urls (up to 5 public HTTPS links to samples or sources: PPTX, PDF, DOCX, XLSX, TXT, MD, CSV, PNG, JPG, up to 25 MiB each and 45 MiB together; the server downloads them). A file the user gave you instead of a link is uploaded first with upload_media (a document up to 10 MiB here), and the url it returns goes into file_urls. Run estimate_presentation first when the user asks the price. If the result has promo_free true the deck was free for this user (say so; list_cost_rub is what it would have cost). Reuse idempotency_key on a retry after a timeout so that one deck is not started twice. Tell the user the deck takes a few minutes.
    ConnectorOAuth
  • Return every JSON-Schema document owned by the authenticated customer (filtered by `customerRef = <auth-principal>`). Excludes global schemas — those are returned by a separate global-list endpoint that lives outside the MCP surface. Each entry is a lightweight `SchemaListDTO` (id, name, type, version) — enough to build a picker UI or to feed an agent's "which schema should I use?" decision. For the full schema content (the JSON-Schema document itself) call the schema-by-id endpoint with the `id` from this list. **Not paginated** — returns the full flat set in one call. This is fine for the legacy per-(type, version) schemas this endpoint was built for, but be aware of the CUSTOM-type caveat below before using it as a CUSTOM schema picker. **CUSTOM-type caveat:** this endpoint lists one row PER VERSION document, not one row per schema group. A CUSTOM group with 5 saved versions shows up here as 5 separate rows, all sharing the same `groupId` but different `id`/`version`. To discover "what custom schema groups does this customer have" (one row per group, with the group's current `latestPublishedVersion`), call scrapewise_list_custom_schema_groups instead — that is the cursor-paginated, one-row-per-group summary and the intended picker source for CUSTOM. Use this endpoint's `groupId` field only to know which group a given version row belongs to (e.g. after finding a version's `id` you want to add a sibling version to). Args: - none — the authenticated customer scope is implicit. Returns: `List<SchemaListDTO>` — zero or more schemas. Each row carries: - id (string): MongoDB ObjectId; use to fetch full content or to attach this schema to a new AI_CONF scraper - name / type / version: enough context for picker UIs and agent decision-making - groupId (string, CUSTOM-only, null otherwise): the schema group this version belongs to. Pass it as `body.groupId` on scrapewise_create_customer_schema to add a new version to this same group. Examples: - Use when: "what schemas do I have?" (non-CUSTOM, or you need per-version detail) — single read, returns the full inventory - Use when: discovering whether a customer schema for a given domain already exists before creating a new one via scrapewise_create_customer_schema - Don't use when: you want a one-row-per-CUSTOM-group summary (with `latestPublishedVersion`, `versionCount`, `scraperRefCount`) → use scrapewise_list_custom_schema_groups instead - Don't use when: you want global schemas too → use the global-schema-list endpoint (currently outside the MCP surface; see scraper-api OpenAPI for administrative tooling) - Don't use when: you need the full JSON-Schema content — this is a summary list; fetch by id for the full document Error Handling: - 200 with empty list if the customer has no custom schemas (not an error). - 401 Unauthorized if no Firebase JWT or API key. - 500 INTERNAL with `correlationId` if Mongo lookup fails. [runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP `outputSchema` is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.
    ConnectorAPI key
  • Use this when a human must publish the DNS records for a custom domain. Requires auth. Inputs: domain_id (required; the dom_… id from cooper_add_domain or cooper_list_domains), expires_in_hours (optional integer from 1 to 168, default 72). Returns {url, expires_at, domain_id, hostname}. url is one page the human opens. It shows the records, a zone file, and Check now. It is not an API key. Creating a link revokes the previous link for that domain. A verified domain can still have a link. Another account's id is domain_not_found. Failure codes: unauthorized, domain_not_found, invalid_body, permission_denied.
    ConnectorNo auth