Skip to main content
Question

Figma Desktop MCP get_metadata forces the get_design_context which cannot be done when targeting a node page

  • January 29, 2026
  • 1 reply
  • 72 views

Stavros Koureas

I am using Figma Desktop MCP with VSCode and I am trying to build a complete prototype (POC) of an app based on designs. So I have created an agent with some instuctions like to get this page node which contains many desings.

 

I have instructed the Agent to use get_metadata, as the page contains many designs and if run get_design_context in the page node it will fallback to get_metadata anyhow. The problem here is that together with the ouput content of the ge t_metadata there is also a note:

“IMPORTANT: After you call this tool, you MUST call get_design_context if trying to implement the design, since this tool only returns metadata. If you do not call get_design_context, the agent will not be able to implement the design.”

 

Issue with this is that if the get_design_context after the get_metadata it picks only the first design it sees. I tried to build an agent skill to parse the page node metadata and export the design nodes which will provided to the agent to iterate over each design node id to get it using the get_design_context. But this is always skipped and I think that this IMPORTANT message it makes my agent unfocusing on the instructions.

 

Am I doing something wrong, or is any other best practice in order to get the design code one by one as all together does not fit to the LLM context?

1 reply

Stavros Koureas

Normally there should be a way / mcp tool to get multiple parent node ids, for each design in a page which might contain multiple designs and then the get_design_context be able to iterate over these ids. Question is how the tool will now which node id is the header of each design, maybe a flag into figma or maybe every top frame inside a page?