Skip to content
English
  • There are no suggestions because the search field is empty.

Use Web MCP: request, prompts, and reviewing changes

This guide walks you through a first request, shows how to write good prompts, and explains how to check a change before it runs. 

Before you begin

Connect Web MCP to your AI app. See Connect Web MCP to your AI app.

Make your first request

  1. Check the connection. Ask: "What Web MCP tools do you have available?" You should see four tools: operations_list, schema_search, schema_details, and graphql_execute.
  2. Look at your workspace. Ask: "List the projects in my LottieFiles workspace and how many animations each contains." The AI looks up the right request, runs it, and shows the results. You may see it use several tools in a row. That's normal.
  3. Get details for one animation. Ask: "Fetch the details of my most recently modified animation, including its CDN link." The AI returns the details and the file's CDN link. You can't download files through Web MCP, but you can open the CDN link to get the file.

Write a good prompt

  • Where: the workspace, project, or animation name.
  • What: list, find, summarize, rename, move, or explain.
  • Which ones: a tag, a date, a status, or a name pattern, such as "drafts" or "tagged onboarding".
  • What you want back: a list, a count, a summary, or a link.
  • Whether to run it: say "draft but don't run" if you only want to see the request first.

Example prompts

  • See what's in a workspace: List the projects in my LottieFiles workspace and how many animations each contains.
  • Find animations: Find every animation tagged 'onboarding' and summarize them.
  • Get a file's CDN link: Fetch the details of my most recently modified animation, including its CDN link.
  • Rename safely: Draft, but don't run, a mutation that renames animation X to "hero-loader-v2".
  • Bulk tidy-up: Rename the draft animations in Project X to match our naming convention. Show me the list of changes before you run them.
  • Learn the API: Find the GraphQL operations related to file uploads and explain what each one needs.
  • Check risk: Which operations in the schema are classified as destructive?

Review changes before they run

Reading your workspace never changes anything. A change (a "mutation") creates, updates, or deletes real data, such as renaming, moving, or deleting an animation. Check any change before it runs, especially anything marked destructive, billing, or admin.

  1. Ask for a draft first. For example: "Draft, but don't run, a mutation that renames animation X to 'hero-loader-v2'."
  2. Check the risk level. Ask: "What is the risk level of this operation?" See Web MCP tools reference for what each level means.
  3. Review the draft. Ask the AI to explain in plain words what will change and which animations are affected. In apps that show built-in prompts, you can use review_graphql_mutation.
  4. Run it. When you're happy, tell the AI to go ahead.
  5. Check the result. Ask the AI to list the affected animations again to confirm the change.

Important: AI assistants confirm before destructive operations, but you are still responsible for what runs. If your app asks permission before each tool call, read what it's about to run before you allow it.