Skip to main content

Trigger specific tools when needed

The MCP supports different tools, and each one provides your AI assistant with a different kind of structured context. But sometimes, the assistant doesn't automatically pick the right one, especially as more tools become available.

That's why it's often helpful to nudge it by calling the tool explicitly in your prompt.

  1. get_code provides a structured React + Tailwind representation of your Figma selection. This is a starting point that your AI assistant can then translate into any framework or code style, depending on your prompt.

  2. get_variable_defs extracts the variables and styles used in your selection (color, spacing, typography, etc). This helps the model reference your tokens directly in the generated code.

Example:​

Several users reported trying to get variable values, but received raw code instead, until they changed the prompt to something like:

Get the variable names and values used in this frame

This clarified the intent and successfully triggered the correct tool.

Bottom line - If the output feels off or missing something, try being explicit about the tool, especially as we add more capabilities.

Note: These recommendations are based on feedback from our alpha and beta users. As the MCP ecosystem improves and usage patterns mature, this list will continue to evolve.